Skip to main content
Glama

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context: upstream source (FRED / Baltic Exchange), the returned signal (trend classification plus five-year average), a per-call price, and a verification URL. However, the payment and attestation boilerplate is repeated rather than elaborated, so it does not deepen behavioral understanding much beyond pricing and provenance.

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?

The purpose, source, and usage conditions are front-loaded and read cleanly. The tail is padded with commercial boilerplate – '$0.02' appears twice, alongside the 'atomic' and 'cryptographically attested' marketing language – which dilutes an otherwise tight definition.

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 parameters and no output schema, the description must carry the return-value burden, and it does name the key outputs (trend classification, five-year average) plus the data source. It could state the return format or index freshness/cadence, but nothing essential for calling it correctly 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 no input parameters, so there are no semantics for the description to add. The baseline for a zero-parameter tool 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?

The description names a specific resource (Baltic Dry Index shipping cost benchmark) plus its source (FRED / Baltic Exchange) and its output shape (trend classification, five-year average). That is more specific than a generic benchmark tool, but it does not explicitly position itself against the many sibling benchmark tools, 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 Guidelines4/5

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

'Use when assessing global trade volume, freight inflation, or supply chain cost pressure' gives clear context for when to call it. It stops short of exclusions or naming an alternative for related freight/commodity questions, so it is context without routing.

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