Skip to main content
Glama

Stratalize Intelligence

Get Retail Sales Benchmark

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds provenance (FRED/Census), unit semantics, cost per call, and a cryptographic attestation with a verification URL. Duplicated pricing text ("$0.02 atomic" and "$0.02 USDC per call") is redundant but the added context is real.

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?

Core purpose and data source are front-loaded in the first sentence, and the use-case sentence follows logically. The trailing pricing/attestation block repeats the price twice and spends a line on promotional verification details, 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?

For a zero-parameter, no-output-schema read tool, the description covers source, units, derived metrics, and cost, which is nearly everything an agent needs to call it. It omits frequency, publication lag/revisions, and the actual response shape, which would have closed the remaining gap.

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; the description still adds value by naming the metric set returned (MoM and YoY percent change in billions USD), which goes beyond an empty schema.

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 gives a specific resource (US advance retail sales), its source (FRED / US Census Bureau), units (billions USD), and derived metrics (MoM and YoY percent change). It is clearly distinct from most siblings by domain, though it does not name a near-neighbor such as get_consumer_sentiment_benchmark to sharpen the boundary.

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?

It lists use contexts (consumer demand monitoring, recession signals, revenue forecasting), which implies when to reach for it, but provides no exclusions, no conditions for preferring an alternative sibling, and no prerequisites or coverage notes (e.g., monthly frequency, advance vs. revised).

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