Skip to main content
Glama

send_feedback

Destructive

Message the Grabblist team: bug, parsing failure, feature request or feedback. Only when the user asks or agrees; show them the text first. Example: type="parsing_failure", tool="add_item", url, message="price not found".

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": {
      "type": "<type>",
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL where it happened
toolNoTool in use, e.g. add_item
typeYesbug, parsing_failure (price/title/image missing), feature_request or feedback
errorNoError text received
messageYesWhat happened or is proposed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / error / description
      Previous value: -"Error message you received, if any"New value: +"Error text received"
    • changedInput schema / properties / message / description
      Previous value: -"What happened or what you propose. Be specific — the team reads this."New value: +"What happened or is proposed"
    • changedInput schema / properties / tool / description
      Previous value: -"The tool you were using when the issue occurred (e.g. add_item, search_saved)"New value: +"Tool in use, e.g. add_item"
    • changedInput schema / properties / type / description
      Previous value: -"Type: bug (something broken), parsing_failure (price/title/image not extracted), feature_request (wishlist), feedback (general feedback)"New value: +"bug, parsing_failure (price/title/image missing), feature_request or feedback"
    • changedInput schema / properties / url / description
      Previous value: -"The URL where the issue occurred"New value: +"URL where it happened"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is covered; the description adds the non-obvious behavioral constraint that the user must consent and see the outgoing text first. It does not describe what confirmation or response the caller gets back, which is the remaining gap. Nothing in the text conflicts with the annotations.

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?

Purpose comes first, the consent constraint second, and a compact worked example last — a good front-loaded ordering with no filler. The fragmentary phrasing of the opening clause and the valueless 'url' in the example cost it a perfect score.

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

Completeness4/5

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

With five fully documented parameters, no output schema, and annotations covering the safety profile, the description supplies everything needed to decide and call: purpose, consent gate, and a parameter example. The only omission is any indication of what happens after submission (confirmation, limits), which is minor for this tool.

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 100%, so the schema carries the baseline, but the trailing example ('type="parsing_failure", tool="add_item", url, message="price not found"') demonstrates how the optional url/tool fields combine with a specific type, which is genuine added meaning. It does not explain the 'error' field, which is left entirely to the schema.

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

Purpose5/5

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

The description names a specific verb and destination ('Message the Grabblist team') plus the exact categories accepted (bug, parsing failure, feature request, feedback). None of the sibling tools (add_item, update_item, delete_item, etc.) do anything similar, so an agent can route to this tool without ambiguity.

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

Usage Guidelines5/5

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

It gives an explicit gating condition: 'Only when the user asks or agrees; show them the text first.' That is both a when-to-use rule and a when-not-to-use rule, plus a required confirmation workflow before invoking. No alternative tool competes for this job, so no cross-reference is needed.

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.

Resources