Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

dispute_finding

INFLUENCE — "you say we lack X, here it is." Send the claim in words and a URL that evidences it. Returns 202; a person fetches your evidence, checks it against what we hold, and emails you either way. Open to any paying caller — you should not have to prove ownership before you can tell us our data is wrong. Priced B4 (human work) — included in Influence; otherwise $49.00 as a one-off with its own receipt, never from a prepaid balance. If this is your own company and our data about it is wrong, report_correction is free. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
slugYesProvider slug — lowercase, hyphenated, as find_providers returns it, e.g. "stripe".
claimYesThe finding you dispute and why, e.g. "We do publish an OpenAPI at /openapi.json".
contactNoOptional email address we can reply to about this request, e.g. "dev@example.com".
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
evidence_urlNoURL that shows the finding is wrong, e.g. "https://example.com/openapi.json".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
  2. Changed4 schema fields changed
    • addedInput schema / properties / claim / description
      Added value: +"The finding you dispute and why, e.g. \"We do publish an OpenAPI at /openapi.json\"."
    • addedInput schema / properties / contact / description
      Added value: +"Optional email address we can reply to about this request, e.g. \"dev@example.com\"."
    • addedInput schema / properties / evidence_url / description
      Added value: +"URL that shows the finding is wrong, e.g. \"https://example.com/openapi.json\"."
    • addedInput schema / properties / slug / description
      Added value: +"Provider slug — lowercase, hyphenated, as find_providers returns it, e.g. \"stripe\"."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only give readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the description carries most of the burden and does deliver: it discloses the 202 response, the human-review-and-email workflow, the no-ownership-required policy, and the pricing ($49 one-off, B4, never from a prepaid balance). Ratings on the response outcome and latency are not given, but the behavioral picture is unusually rich.

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

Conciseness3/5

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

The action is front-loaded, but the 'INFLUENCE — "you say we lack X, here it is"' framing and the dense pricing/policy sentences add verbosity ahead of the operational facts. Several sentences do earn their place (pricing, ownership, alternative), but the register is padded.

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 no output schema, the description usefully explains the return lifecycle (202, human verification, email either way), eligibility, pricing, and the sibling alternative. It is close to complete for a submission tool, though it could state expected turnaround or what 'checks it against what we hold' yields.

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 100%, so all five parameters (slug, claim, contact, context, evidence_url) are already documented in the schema. The description only restates 'the claim in words and a URL' — it adds no syntax, format, or constraint meaning beyond the schema, so the baseline 3 applies.

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 concrete action — 'Send the claim in words and a URL that evidences it' — so an agent knows it submits a dispute with evidence. It also names a sibling (report_correction) and the condition that selects it. The 'INFLUENCE — ...' marketing opener somewhat obscures the verb at the front, keeping it short of a clean 5.

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?

Explicitly says who may call it ('Open to any paying caller') and when to use the alternative ('If this is your own company and our data about it is wrong, report_correction is free'). This gives an agent a clear routing rule, though no explicit 'do not use for X' exclusions beyond the report_correction case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources