Skip to main content
Glama

get_retail_sales_benchmark

Read-only

US advance retail sales from FRED in billions USD with month-over-month and year-over-year percent change. Use for consumer demand monitoring, recession signals, and revenue forecasting agents. Source: FRED / US Census Bureau. $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_retail_sales_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, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful non-schema context: upstream provenance (FRED / US Census Bureau), per-call cost ($0.02 USDC), and a settlement receipt with a verification URL. It does not disclose data freshness, release lag, or historical depth, which keeps it from a 5.

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?

The data definition is front-loaded and efficient, but two of the four sentences are promotional/attestation boilerplate (post-quantum signed receipt, verify URL) that does not help an agent decide or invoke. The pricing line earns its place; the cryptographic framing is close to filler for invocation purposes.

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, single-series tool with no output schema, the description covers source, units, returned measures, and cost. What is missing is the time dimension: frequency, history window, and whether values are latest-vintage or revised, which an agent would need to use the result responsibly.

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 there is no parameter meaning to add and the schema cannot be deficient. The description notes the returned measures (MoM and YoY percent change), which is return information rather than parameter semantics; baseline 4 applies for a no-parameter tool.

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 a specific dataset (US advance retail sales from FRED), its units (billions USD), and the derived metrics returned (month-over-month and year-over-year percent change). This is enough to distinguish it from adjacent benchmarks such as get_consumer_sentiment_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 usage contexts: consumer demand monitoring, recession signals, and revenue forecasting agents. It stops short of saying when not to use it or naming a sibling series to prefer for related questions, so the agent must infer boundaries, but the positive guidance is clear.

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