Skip to main content
Glama

report_road_condition

Submit a crowdsourced road-condition report (requires auth + road:write).

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": {
      "location": "<location>",
      "type": "<type>",
      "severity": "<severity>"
    },
    "name": "report_road_condition"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
api_keyNo
locationYes
severityYes
evidence_refsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The description adds real value beyond annotations by naming the required auth and 'road:write' scope, which the annotation block does not convey. However, it omits behavior the annotations imply but don't explain: idempotentHint=false means repeated calls create duplicates, and nothing says how evidence_refs are validated or what the report affects downstream.

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?

A single tight sentence with the action front-loaded and the auth constraint trailing as a qualifier — no filler. It is arguably under-specified rather than padded, which is a different problem than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with five parameters, a nested object, zero schema descriptions and no enums, the description is far too thin; an output schema exists so return values needn't be covered, but the agent still lacks enough to construct 'location', 'severity' or 'type' correctly. The auth note is the only substantive addition.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description carries the full burden and provides essentially nothing: it never explains 'type' (no enum), the 'severity' integer scale, the shape of the nested 'location' object, or what 'evidence_refs' should point to. Only 'api_key' is self-evident.

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?

States a specific verb and resource ('Submit a crowdsourced road-condition report'), which clearly separates it from read-oriented siblings like get_road_incidents or get_route_conditions. It does not explicitly name a sibling it replaces, but the write-vs-read distinction is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is a parenthetical auth/scope requirement. There is no statement of when an agent should file a report versus reading existing incidents, no prerequisites beyond the scope string, and no guidance on duplicate submissions or which conditions warrant reporting.

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.