Preview a note before adding it to a security case, enabling validation of content, type, and visibility settings.
Preview adding a note to a case.
| Name | Required | Description | Default |
|---|---|---|---|
| oid | Yes | ||
| content | Yes | ||
| is_public | No | ||
| note_type | No | ||
| case_number | Yes | ||
| token_ttl_seconds | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description gives no behavioral details—e.g., whether it actually performs or simulates the addition, permission requirements, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
While very short, the description is underspecified rather than concise; it fails to earn its place by adding value beyond the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the 6 parameters, absence of annotations and output schema, the description is grossly incomplete and insufficient for an agent to use this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage and no parameter explanations in the description, the agent has no guidance on the meaning or usage of the 6 parameters beyond their names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Preview adding a note to a case' states the action (preview add) and resource (note to a case), but does not clarify what 'preview' entails or distinguish it from many sibling preview tools like lc_preview_add_case_artifact.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus other preview tools or alternatives. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/geoffbelknap/limacharlie-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server