BusCalc — Business & Trade Calculations

Bridge clearance screening

buscalc_map_bridge_screen

Read-onlyIdempotent

Screen one mapped route leg of up to 250 miles against the dated National Bridge Inventory. Posted signs govern. Put tool fields inside inputs. Supply units or modelVersion only when listed in inputSchema. Follow its required fields and exact choices. Do not pass the REST calculator field inside MCP arguments.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputs": {
        "to": 245,
        "from": 225,
        "state": "TX",
        "routeId": "IH0035-KG",
        "heightIn": 162
      }
    },
    "name": "buscalc_map_bridge_screen"
  }
}

Input Schema

Name	Required	Description	Default
`inputs`	Yes
`modelVersion`	No

Output Schema

Name	Required	Description	Default
`kind`	Yes
`items`	Yes
`notice`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description earns credit for going beyond them: calling the inventory 'dated' and stating 'Posted signs govern' tells the agent results are advisory screening, not authoritative clearance. It does not mention what happens when a leg exceeds 250 miles, which keeps it off a 5.

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 purpose is correctly front-loaded in one tight sentence, but the following sentences are a mix of formatting boilerplate and one instruction ('do not pass the REST calculator field') that reads as harness plumbing rather than tool semantics. The result is short but not every sentence earns its place.

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

Completeness3/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 need no explanation, and the dataset caveat is present. What is missing for a tool with a nested required object and unit-sensitive numeric fields is any account of coordinate semantics or overflow behavior past the 250-mile cap.

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%, so the description must compensate for the nested inputs object. It only clarifies the wrapper layout and that modelVersion must match the listed enum; the meaning of 'from' and 'to' (presumably mile markers along the route), 'heightIn', and 'marginIn' default semantics are left entirely to the schema's types and bounds.

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 first sentence states a specific verb (screen) and resource (one mapped route leg, up to 250 miles) against a named dataset (National Bridge Inventory). That scope cleanly separates it from trip-planning or lookup siblings. It stops short of naming an alternative tool, so it does not reach the top of the scale.

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 remaining sentences are invocation mechanics ('put tool fields inside inputs', 'follow its required fields') rather than when-to-use guidance. No alternative is named, no precondition is given beyond the 250-mile leg limit, and nothing says when another bridge or route tool would be the better choice.

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

All BusCalc — Business & Trade Calculations tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?