Othermile border costs

Real border outcomes

border_lane_insights

Read-onlyIdempotent

What shoppers and sellers actually paid and how long parcels actually took on a route, from real reports. Only shown when enough reports exist.

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": {
      "to": "<to>"
    },
    "name": "border_lane_insights"
  }
}

Input Schema

Name	Required	Description
`to`	Yes
`from`	No	Two letter country code, for example CA or US
`mode`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedOct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact beyond them: results only appear once a sufficient volume of reports exists. It stops short of saying whether insufficient data yields an empty result or an error, or what the threshold is.

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?

Two short sentences with no filler, leading with the outcome data before the availability caveat. Minor ambiguity in 'Only shown' (shown where?) keeps it from being a clean 5.

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 no output schema, the description should describe the shape of the returned data; it says what is measured (price paid, duration) but not granularity, aggregation (averages, ranges, counts), or per-mode breakdown. Combined with undocumented enum parameters, an agent can identify the tool but must guess at what it will actually receive.

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 coverage is only 33%: 'from' is documented while 'to' and 'mode' carry bare enums with no descriptions. The description never mentions any parameter, so it does not explain the semantics of courier vs mail, nor why 'to' is restricted to CA/US while 'from' accepts any two-letter code. It fails to compensate for the low coverage.

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 description names the specific resource: actual prices paid and actual transit times observed on a route, sourced from real reports. That clearly distinguishes it from an estimate or quote tool, but it never names border_quote or door_cost_estimate as the contrasting alternatives, so differentiation is inferred rather than stated.

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?

'from real reports' and 'Only shown when enough reports exist' imply this is for checking historical, observed outcomes rather than a fresh estimate. However, there is no explicit 'use this when...' guidance and no stated exclusion or sibling routing, leaving the agent to infer that border_quote is the pre-shipment alternative.

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

All Othermile border costs 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?