Lane Cost freight rates

Find a place

search_places

Read-onlyIdempotent

Look up US cities by the start of their name, or ZIP codes by their first digits. Use it when a place is not found by the other tools.

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": "search_places"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Start of a city name, optionally with a state ("spring il"), or three or more digits of a ZIP.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorldHint=false, so the safety profile is covered. The description still adds genuine behavior beyond that: US-only scope and prefix-based (not substring) matching, both of which affect how an agent should phrase queries. It omits what the response looks like when multiple places match.

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?

Two short sentences, zero filler, with the matching rule front-loaded before the usage hint. Nothing is redundant or buried.

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?

With one required parameter and annotations covering safety, the essentials are present. But there is no output schema and the description never indicates whether a lookup returns a single place or a list of candidates, nor how to handle ambiguity or no-match, which is the main remaining gap for a fallback lookup tool.

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 coverage is 100% and the schema's query description already specifies the 'spring il' style and 'three or more digits' for ZIPs. The description's phrasing largely restates that, adding no new format, normalization, or edge-case meaning, so the baseline 3 applies.

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 with matching semantics: 'Look up US cities by the start of their name, or ZIP codes by their first digits.' That is far more informative than the title 'Find a place' and clearly separates it from the rate/equipment siblings. It stops short of naming any alternative tool explicitly, so it lands at 4 rather than 5.

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?

'Use it when a place is not found by the other tools' gives a fallback condition, which is real usage guidance. However, 'the other tools' is unnamed and no exclusion or positive primary-use case is given, so the agent must infer the selection rule.

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

All Lane Cost freight rates tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?