Skip to main content
Glama

Tell the team what you need

send_feedback

Report data or a feature you needed and could not get, wrong data, or anything confusing. Be specific about league, stat, field and what you were trying to do. Optionally rate how well the last result served the task, 1 to 5; a rating alone is enough. Leave out personal data. Needs no key and costs no quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomissing_data
agentNoYour agent or client name.
momentNoThe moment from meta.feedback, when answering one.
ratingNoOptional. How well the last result served the task, 1 to 5.
messageNoWhat you needed or what went wrong, 3 to 2000 characters. Optional when a rating is sent.
blockingNoTrue if this stops the task.
endpointNoThe tool or endpoint involved.
use_caseNoWhat is being built, up to 500 characters.
got_what_neededNoWhether the data met the task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is already conveyed. The description adds genuinely new operational facts not in annotations: it needs no API key and consumes no quota, plus a privacy constraint ("leave out personal data"). It does not say what happens after submission or whether a response is returned, which keeps it from a 5.

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?

Three compact sentences lead with the triggering conditions, then content requirements, then the rating shortcut and operational facts. Nothing is padding, though the opening enumeration is slightly run-on and could be tightened.

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?

For a nine-parameter, all-optional write tool with 89% schema coverage and no output schema, the description covers purpose, minimum viable invocation, content expectations, privacy, and quota cost. It leaves the post-submission behavior and the `moment`/`endpoint` fields largely to the schema, which is acceptable given the coverage.

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 description coverage is 89%, so the schema already explains most of the nine parameters, making 3 the baseline. The description adds a little guidance on message content (specify league, stat, field and intent, 3-2000 chars implied) and reiterates the 1-5 rating with the note that a rating alone suffices. It does not explain the `moment`, `endpoint`, or `blocking` parameters, which the schema partially covers.

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 gives a specific verb (report) and enumerates the resources involved: missing data, missing feature, wrong data, and anything confusing. It is clearly distinguishable from every sibling, which are all data-retrieval or auth tools. It stops short of stating explicitly that the report goes to the development team, which the title carries instead.

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?

"Report data or a feature you needed and could not get, wrong data, or anything confusing" clearly defines the triggering conditions for calling the tool, and "a rating alone is enough" clarifies a low-effort invocation path. There is no explicit when-not guidance or named alternative, but no sibling competes for this purpose.

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