Skip to main content
Glama

Superpass

Send feedback

send_feedback

Use this when the person asks to send feedback about Superpass, or when a Superpass tool could not do what they asked. Write a sentence or two about Superpass: what failed or what was missing, and the tool it was about. Never include the conversation, names, document numbers or anything else personal.

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": {
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesproblem, idea or question
textYes
toolNo

Output Schema

NameRequiredDescriptionDefault
sentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, and the description adds real content not available structurally: the privacy constraint forbidding conversation content, names, and document numbers, plus a 'one or two sentences' scope on the payload. It does not say where the feedback goes, whether it is anonymous, or whether the user should confirm before sending.

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

Conciseness5/5

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

Two sentences: the first front-loads the trigger conditions, the second constrains the payload content and its privacy limits. Nothing is redundant with the schema or annotations.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. What an agent needs in order to file a correct, privacy-safe report — when to trigger, what to write, what never to include, and which tool to name — is all present.

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

Parameters3/5

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

Schema coverage is only 33% — 'text' and 'tool' have no schema descriptions, and the 'kind' enum's schema description merely restates its values. The description partially compensates by explaining that 'text' should describe what failed or was missing and that 'tool' identifies the tool in question, but it gives no guidance on choosing problem vs. idea vs. question, leaving the enum's semantics thin.

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 states a specific verb and resource ('send feedback about Superpass') and makes the domain of the tool unmistakable, which also separates it from the unrelated siblings (chip location, country lists). It never quite says who receives the feedback or that it is an outgoing write, but the action is clear.

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 two explicit and non-overlapping trigger conditions: the person asks to send feedback, or a Superpass tool could not do what they asked. The second condition is the kind of proactive routing guidance most definitions omit, and there are no competing tools to disambiguate against.

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