Skip to main content
Glama

logistics_route_brief

Read-only

Route & shipment brief (bundle) — One call: estimated driving distance and time between two US points (addresses or lat,lon), an estimated fuel cost, and weather + active alerts at both ends, fused into a go/caution verdict. JSON. Price: $0.05 USDC (Base, via x402).

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": {
      "origin": "<origin>",
      "dest": "<dest>"
    },
    "name": "logistics_route_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpgNooptional vehicle MPG (default 25)
destYesdestination address or 'lat,lon'
originYesorigin address or 'lat,lon'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely new operational context: it is a paid call ($0.05 USDC on Base via x402), the output is JSON, and the result is a synthesized go/caution verdict rather than raw data. It stops short of describing failure modes (unresolvable addresses, partial weather coverage) or whether payment is charged on error.

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?

Dense and front-loaded — the payload contents come first, then output format, then price. The opening 'Route & shipment brief (bundle)' restates the annotation title, and the two trailing fragments ('JSON.' / 'Price: ...') are terse to the point of choppiness, but nothing is wasted.

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 carries the return-value burden and does so by enumerating the fused fields and the verdict. For a three-parameter read-only tool it is nearly complete; only error/partial-result behavior and the meaning of the go/caution thresholds are absent.

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 origin/dest/mpg are already documented with their formats and the 25 MPG default. The description reinforces 'addresses or lat,lon' and US-only scope but adds nothing about the mpg parameter or input validation, so the baseline 3 applies.

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?

Names a specific bundle with concrete contents: driving distance/time between two US points, estimated fuel cost, weather and active alerts at both ends, fused into a go/caution verdict. The aggregation scope plus the 'US points' constraint makes it clearly distinct from the other single-domain *_brief siblings.

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

Usage Guidelines3/5

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

'One call' implies it should be preferred over fanning out to individual tools, and the US-only limitation gives an implicit boundary, but there is no explicit when-to-use/when-not-to-use statement or named alternative. Usage must be inferred rather than read.

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.

Resources