Skip to main content
Glama

Report a wrong value

report_issue

Reports a suspected error in data this service returned, for one series or one endpoint, to the operator: a kind from a fixed list and an optional short text (at most 500 characters), e.g. country, period and the value the publisher shows. Side effects: only stores the report for a manual check against the source; it changes no data, returns no data, and nobody replies. Text that looks like an email address, phone or account number is refused and not stored. When to use: only when a value from this service disagrees with its source or is clearly broken, not for questions or data requests. No API key; at most 10 reports a day per client, not counted against the data quota.

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

Input Schema

NameRequiredDescriptionDefault
kindYesWhat is wrong
textNoShort details, no personal data
apiIdNoEndpoint id the value came from, e.g. fx-currency-convert (call_api or ask_anything), in place of series
paramsNoThe params of that call_api call, so the same answer can be checked
seriesNoSeries id the value came from, e.g. fx.EUR.USD (get_series or a candidate)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the report is only stored for manual review, that no data is changed or returned, that no one replies, that PII-like text is refused before storage, and that the limit is 10 reports/day not counted against quota. This is exactly the mutation/limit/permission context the hints (readOnlyHint=false, destructiveHint=false) cannot convey.

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?

Dense and front-loaded — purpose first, then side effects, then when-to-use, then access limits — with essentially no filler sentences. The single run-on paragraph with stacked parentheticals makes it slightly harder to scan than it needs to be.

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?

For a write-ish tool with no output schema, the definition covers everything an agent needs: what it does and does not do (no data change, no return value, no reply), input constraints, PII refusal, and rate limits. Nothing material is left to inference.

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 100%, so the baseline is 3; the description still adds value by framing the target as one series or one endpoint ('in place of series') and by giving the shape of good text (country, period, value the publisher shows) on top of the 500-char cap. The kind enum itself is left 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?

States a specific verb and object — reporting a suspected error in data this service returned — and scopes it to 'one series or one endpoint'. That scope is enough to separate it from siblings like get_series or call_api, which retrieve data rather than file complaints.

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?

'When to use: only when a value from this service disagrees with its source or is clearly broken, not for questions or data requests' gives an explicit trigger plus an explicit exclusion. It does not name a sibling to route to for the excluded cases, which keeps it from a 5.

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