Skip to main content
Glama

get_traffic_congestion

Read-only

Traffic sub-module congestion estimate for a corridor.

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": {
      "corridor": "<corridor>"
    },
    "name": "get_traffic_congestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
corridorYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that: no indication of whether the estimate is live or forecast, what time horizon applies, what units or scale congestion is reported on, or any coverage limits for a corridor.

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?

A single short sentence with no waste and the resource front-loaded, but it is under-specified rather than concise. The brevity costs information an agent needs to call the tool correctly.

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?

An output schema exists, so return values needn't be explained, but the input side is entirely unexplained for the one required parameter. For a tool whose sole argument is a free-form string with no documented format, the description leaves a critical gap.

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% for the single required parameter, so the description carries the full burden of explaining 'corridor'. It only restates the parameter name — no format, no example (road name vs. ID vs. coordinate pair), no hint about corridor length or endpoints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does state a resource and an output ('congestion estimate') scoped to a corridor, so the agent knows roughly what comes back. However, 'Traffic sub-module' is internal jargon that conveys nothing, and nothing distinguishes this from siblings like get_road_incidents or get_route_conditions.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to an alternative tool. The agent must infer from the name alone that this is the congestion tool rather than the incidents or route-conditions tool.

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.