Skip to main content
Glama

Stratalize Intelligence

Get Shipping Cost Benchmark

get_shipping_cost_benchmark
Read-only

Baltic Dry Index shipping cost benchmark from FRED with trend classification (elevated, depressed, normal) and five-year average. Use when assessing global trade volume, freight inflation, or supply chain cost pressure. Source: FRED / Baltic Exchange. $0.02 atomic. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds value beyond that: the upstream source (FRED / Baltic Exchange), the output shape (trend classification plus five-year average), the per-call price in USDC, and the attestation/verification path. The only weakness is that the cost and attestation claims read as promotional boilerplate rather than operational detail.

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?

Purpose, output shape and use case are front-loaded, which is good. But the pricing is stated twice ('$0.02 atomic' and '$0.02 USDC per call'), and the post-quantum receipt / verify URL sentence is marketing text that does not help an agent decide or invoke. Those redundant clauses cost it a point.

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?

For a zero-parameter read tool with no output schema, the description carries the needed burden: it names the source, the classification categories, the five-year average, and the cost. An agent knows what it will get and what it will pay. It could be slightly more complete by noting the unit or frequency of the index value, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to add. The description correctly implies a no-argument call and never suggests any inputs are needed.

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?

The description names the specific resource (Baltic Dry Index shipping cost benchmark from FRED) and states exactly what is returned: trend classification (elevated, depressed, normal) plus a five-year average. That is enough to distinguish it from siblings such as get_construction_cost_benchmark or get_commodity_benchmark without opening any schema.

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

Usage Guidelines4/5

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

It gives explicit use cases — assessing global trade volume, freight inflation, or supply chain cost pressure — which is real context rather than an implied purpose. It stops short of naming a when-not condition or routing the agent to a neighboring benchmark tool, so it falls just short of a 5.

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