Skip to main content
Glama

Send feedback

submit_feedback

Tell us how a call went

Reference the call_id of any earlier response and say whether it helped, and optionally why, in a sentence about the result — what was right, missing or wrong. Do not include the user's words, the conversation, or anything about the person. Nothing is overwritten: sending again for the same call adds a new version and keeps the earlier ones (up to 50 per call). Lightly rate-limited.

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": {
      "call_id": "<call_id>",
      "outcome": "<outcome>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoAbout the result only — never the conversation or the user.
call_idYes
outcomeYes

Output Schema

NameRequiredDescriptionDefault
call_idNo
versionNoWhich submission for this call this is (1 for the first); earlier ones are kept.
recordedNo
doc_notesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / version
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Which submission for this call this is (1 for the first); earlier ones are kept."
      +}
  2. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it discloses that previous feedback is preserved rather than overwritten, that resubmission creates new versions capped at 50 per call, that the tool is lightly rate-limited, and that private conversation/user details must not be included. This is consistent with destructiveHint=false and idempotentHint=false.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and then supplies useful constraints without excessive length. There is slight redundancy with the notes parameter description, but every sentence contributes relevant guidance.

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

Completeness5/5

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

Given the annotations, output schema, and three-parameter schema, the description is complete enough for correct invocation. It covers purpose, privacy constraints, versioning behavior, rate limiting, and resubmission semantics.

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

Parameters4/5

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

Schema description coverage is low at 33%, so the description carries meaningful extra burden. It explains that call_id refers to an earlier response, that notes should describe only the result and never the conversation or user, and that outcome is about whether the call helped; it does not explicitly define each outcome enum value, but the overall semantics are clear.

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

Purpose4/5

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

The description clearly states that this tool submits feedback about a call and explains the core action of referencing a call_id and reporting whether it helped. It is easily distinguishable from the unrelated sibling tools, though the phrasing is conversational rather than a crisp verb-resource statement.

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

Usage Guidelines4/5

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

It gives clear usage context: reference an earlier response via call_id, say whether it helped, and optionally explain why. It does not name alternatives or explicit when-not-to-use conditions, but the siblings are unrelated so the guidance is sufficient.

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.