Skip to main content
Glama

inflation-signal

by com.airblockfz

scan_bottoms

Scan all 45 macro series and return those reading LOWEST (deflation-side / liquidity-bottom), ranked most-low first. 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. BEST COLD START: you do not need to pick a symbol — this ranks the whole universe for you. The free pitch tool tells you HOW MANY are at a bottom right now; this names them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many to return (default 5, max 45)

TDQS

A4.1/5.0
Behavior4/5

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

Discloses payment requirement ($0.01 via x402), trial period, no account needed, and retry header handling. No annotations exist, so description carries full burden. Could mention rate limits or error states for 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One paragraph with front-loaded purpose. Payment details are necessary but could be separated. No wasted sentences.

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?

Covers purpose, payment, trial, cold start, sibling distinction. Lacks output format description, but no output schema exists. Adequate for a 1-param list tool.

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

Parameters3/5

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

Only one parameter 'limit' with schema description coverage 100%. Tool description adds no extra meaning beyond schema. Baseline 3 applies.

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?

Clearly states verb 'scan', resource 'all 45 macro series', and output ordering 'LOWEST... ranked most-low first'. Distinguishes from sibling 'scan_tops' by describing opposite use, and from 'pitch' which tells how many are at bottom.

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?

Provides explicit context: 'BEST COLD START: you do not need to pick a symbol'. Mentions payment and free alternative 'pitch'. Lacks explicit when-not, but sibling names imply when to use the opposite tool.

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