Skip to main content
Glama

Report feedback about this server

report_feedback

Use this when one of this server's tools errored, returned wrong or incomplete results, ignored a parameter, or is missing for the user's task. Sends a report to the Only Recipes developers. Include what you called, what came back, what you expected, and a concrete proposed fix. Do not include the user's personal data. Call at most once per distinct issue.

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>",
      "summary": "<summary>"
    },
    "name": "report_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesbug: a tool misbehaved; idea: a missing tool or parameter; question: a description is unclear
toolNoThe tool the report is about
summaryYesWhat you tried, what you got, what you expected
severityNohigh: the user's task could not be completed
argumentsNoThe arguments you passed, as JSON text, without personal data
proposedFixNoA concrete change that would fix it

Output Schema

NameRequiredDescriptionDefault
idNo
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already disclose that this is a non-read-only, open-world, non-idempotent operation without destructive effects. The description adds meaningful behavior beyond that: the report is sent to the Only Recipes developers, should include evidence and a proposed fix, must exclude personal data, and is rate-limited to once per distinct issue.

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?

The description is compact and front-loaded with the triggering conditions, followed by reporting requirements and constraints. Every sentence contributes practical guidance without repetition.

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 rich schema, annotations, and output schema, the description covers the remaining operational context an agent needs: when to file, what evidence to include, what not to include, and how often to call. Nothing material is missing for correct invocation.

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 coverage is already 100%, so the parameters are fully documented. The description still adds useful meaning by clarifying what the summary should contain: what was called, what came back, what was expected; and by emphasizing a concrete proposed fix and omission of personal data.

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: it sends a feedback report to the Only Recipes developers when one of this server's tools misbehaves. The trigger conditions are concrete enough to distinguish it from the recipe-oriented sibling tools, though it does not explicitly name an alternative reporting path.

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 explicit when-to-use conditions: a tool errored, returned wrong or incomplete results, ignored a parameter, or is missing for the user's task. It also gives exclusions and constraints: do not include personal data and call at most once per distinct issue.

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