Skip to main content
Glama

CarlNotes

Read rating note

read_finding_rating_note
Read-only

Restore the connected account's own note to Carl in the CarlNotes finding rating field.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "finding_id": "<finding_id>"
    },
    "name": "read_finding_rating_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
finding_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations declare readOnlyHint=true, but the description uses the write-oriented verb "restore," which implies modifying state. This directly contradicts the read-only annotation and provides no other behavioral context such as what is returned or whether any state changes occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is front-loaded with the confusing verb "restore" and unexplained jargon rather than a clear statement of the read action. It is concise but not well structured for comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with one required parameter and no output schema, the description should clarify what is read and what is returned. Instead it leaves the parameter meaning and return behavior unstated, making it incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single finding_id parameter is undocumented in the schema. The description references a "finding rating field" but does not explain what finding_id identifies, its format, or how it relates to the note being read.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says "Restore the connected account's own note to Carl in the CarlNotes finding rating field," which does not clearly state a read operation despite the tool name. The verb "restore" suggests mutation, and terms like "Carl" and "CarlNotes" are unexplained internal jargon, leaving the actual purpose ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as read_notes or read_finding_rating_note's siblings. The description offers no context, prerequisites, or exclusions to help an agent choose correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.