Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

sf_v1_truck_sleep_stops

Fetch sleep stops for one of 2 corridors — $0.05 per call Origin: https://storefront-data-hms.ares-hms.workers.dev. Price: $0.05 per call via x402 (USDC on Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sf_v1_truck_sleep_stops"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDestination city/state, e.g. "St. Louis, MO" or "Denver, CO"
fromNoOrigin city/state, e.g. "Columbus, OH" or "Chicago, IL". Loose prefix matching: \"Columbus\" matches \"I-70\" origin, \"Chicago\" matches \"I-80\" origin
hos_hoursNoRemaining hours-of-service drive window, e.g. 4.5
x402_paymentNoOptional. X-PAYMENT header value an x402 client produced after settling this exact origin+params challenge. Omit to first receive the Payment Required challenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the non-obvious commercial behavior: a $0.05 per-call charge settled via x402 in USDC on Base, plus the service origin. It does not describe what a 'sleep stop' record contains, how the payment challenge/retry flow behaves beyond the schema's x402_payment field, or any error or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The price is stated twice in near-identical wording ('$0.05 per call' appears twice), and the bare origin URL is spliced into the middle of a sentence, breaking the flow. The corridor-scoping information that would actually matter is the part left out.

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?

Four optional parameters, zero required ones, no output schema, and no annotations mean the description should explain what a valid minimal call looks like and what comes back; it does neither. An agent could invoke this with an empty argument object and have no expectation of the result or whether that satisfies the payment flow.

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 the schema already documents from/to, hos_hours, and x402_payment in detail, including the loose prefix matching quirk. The description adds no parameter meaning beyond that, which meets the baseline for a fully documented schema.

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 gives a specific verb and resource ('Fetch sleep stops'), but scopes it to 'one of 2 corridors' without naming either corridor, leaving the agent unable to tell what data set it is querying. It also makes no attempt to distinguish itself from the sibling truck-oriented tool sf_v1_truck_fuel_prices.

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 or when-not-to-use guidance and no named alternative. The only condition mentioned is a price, not a selection criterion, so an agent has no basis for choosing this over sf_v1_truck_fuel_prices or deciding which corridor request is appropriate.

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.