Skip to main content
Glama

Report that a tool does not work

report_problem
Idempotent

Tell AgentViva that a tool it watches publicly does not work for you or your user, by name ("Notion") or address ("notion.so"), with an optional short note of what happened. AgentViva checks it again right away (at most once an hour per tool) and answers with what that check saw. A report never changes the tool's state by itself: only AgentViva's own checks do, and several must agree. One report per network, tool and day is counted. No API key needed. For a tool AgentViva does not watch, use check_url instead.

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": {
      "query": "<query>"
    },
    "name": "report_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat happened, in a few words (optional).
queryYesA tool name or an address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses a re-check cadence capped at once per hour per tool, that a report alone never mutates the tool's state and that several agreeing checks are required, a counting rule of one report per network/tool/day, and that no API key is needed. It also describes what the response contains - the result of the immediate check - which is valuable since there is no output schema.

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?

A single tight block that front-loads the action, then the side effect, cadence, counting rule, auth, and the routing alternative. Each sentence carries distinct operational information with no filler.

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 two-parameter write-ish tool with no output schema, the description covers side effects, rate limits, counting, auth, and return content, which is nearly everything an agent needs. A small gap remains around what happens when the tool name is ambiguous or the check disagrees with the report.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds real meaning: query accepts either a name ("Notion") or an address ("notion.so"), and note is an optional short account of what happened. That maps the parameters to concrete accepted value shapes rather than restating them.

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 resource - tell AgentViva that a watched tool does not work - and immediately scopes it to tools AgentViva watches, naming check_url for the tools it does not. An agent can distinguish this from check_url and lookup_tool without opening any schema.

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?

Gives the condition for use (the tool is watched and fails for you or your user) and an explicit exclusion with the alternative to use instead (check_url for unwatched tools). No inference about alternatives is required.

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.