Skip to main content
Glama

inflation-signal

by com.airblockfz

evaluate_symbol

Return the inflation-thermometer verdict for one official macro series (45 covered: US-CPI, US-PCE, US-PPI, US-FED Fed assets, US-RRP reverse repo, US-M2, KR-CPI, JP-CPI, DE-CPI … 10 countries + US liquidity/rates/jobs). inflState = too_low|low|normal|high|too_high, score -100..+100 (low>0, high<0). Includes latest official reading (YoY % / balance / rate) and release period. Snapshot-based. Informational only. PAY: $0.01 per call via x402 (USDT on X Layer) — your FIRST paid call opens a 6-day trial at that price. No account, no signup, no commitment; retry with the PAYMENT-SIGNATURE header when you get the 402 challenge. The free pitch tool shows a live verdict for this market's showcase symbol only — this tool answers ANY symbol and adds the per-indicator breakdown behind the score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSeries key, e.g. US-CPI, KR-CPI, US-FED

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, but the description fully discloses behavioral traits: it is snapshot-based, informational only, and has a payment requirement ($0.01 per call, first call opens trial). It also explains the PAYMENT-SIGNATURE header for handling 402 challenges. No contradictions.

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 description is somewhat long but well-structured, front-loading the main purpose and output, then covering payment details and sibling comparison. Every sentence provides useful information, though it could be slightly more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description explains the output format (inflState, score, latest reading, release period). It also sets expectations about payment and limitations, making it complete for the tool's purpose.

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?

Schema coverage is 100% with a brief description for 'symbol'. The tool description adds significant context by listing example values (US-CPI, KR-CPI, etc.) and explaining that the parameter is a series key for 45 covered series, enriching the schema.

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 clearly states the tool returns an inflation-thermometer verdict for one official macro series, listing covered series and output fields. It distinguishes itself from the sibling 'pitch' tool by specifying that this tool answers any symbol and provides per-indicator breakdown.

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

Usage Guidelines5/5

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

The description explicitly contrasts with the free 'pitch' tool, noting that 'pitch' only shows a live verdict for a showcase symbol, while this tool answers any symbol and adds breakdown. It also mentions payment terms and that it's snapshot-based and informational only, guiding the agent on when to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All inflation-signal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: pitch for onboarding, rate for feedback, evaluate_symbol for a single series, and scan_bottoms/scan_tops for global scans. No overlap.

Naming Consistency3/5

Core tools (evaluate_symbol, scan_bottoms, scan_tops) follow a verb_noun pattern, but free tools (pitch, rate) are single verbs, creating a minor inconsistency.

Tool Count5/5

Five tools is well-scoped for a specialized inflation signal server, covering onboarding, feedback, single-symbol queries, and global scans.

Completeness4/5

The tool surface covers the main use cases (single evaluation, top/bottom scans), though a tool for listing available symbols or historical data is missing, but not critical.

Resources