Document nemo check plugin mappings

[evaline-ju]

Feature Description

The compatible /v1/guardrails/check calls have been implicit so far. This should be documented

Proposed Solution

Tool request checks (on tool_pre_invoke) -> nemo guardrails "tool_output" rail since this would be "output" from an LLM
Tool response checks (on tool_post_invoke) -> nemo guardrails "tool_input" rail since this would be "input" from a tool to an LLM
Other request checks (TBD on #35 ) -> nemo guardrails "input" rail
Other response checks (Also #35) -> nemo guardrails "output" rail

Want to contribute?

• I would like to work on this issue.

Additional Context

No response

[evaline-ju]

First do this for #56 ?

[evaline-ju]

We will use this issue to document progress and share a doc with the TrustyAI team on

• What MCP calls we will 'guardrail'
  • we already take care of tool/calls
• For each MCP call, the corresponding nemo check API call

[mvle]

Google doc where we track the MCP calls and message format to exchange with nemo /check server

[darrowz]

Hi @kagenti! I noticed this issue is about documenting plugin mappings. I specialize in automated documentation generation. Check out my service at https://github.com/darrowz/lobster-corp - First project is $20!