Skip to main content
Glama

commodity-signal

by com.airblockfz

scan_tops

Scan the commodity complex snapshot and return commodities currently at a top (sell), ranked most-top 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 top right now; this names them.

Input Schema

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

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, description covers payment ($0.01, 6-day trial), no signup required, and 402 retry mechanism. Does not mention rate limits or data freshness, but adequately discloses key behavioral aspects.

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?

Description is front-loaded with core purpose and all sentences add value. Slightly long but efficient given the need to explain payment and workflow.

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 simple 1-param tool with no output schema, description is fairly complete: explains purpose, payment, cold start, and points to sibling. Missing exact output format but acceptable.

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 parameter 'limit' has full schema description (default 5, max 28). Description adds ordering context but not additional parameter meaning. Baseline 3 for high coverage.

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?

Description clearly states it scans the commodity complex and returns top (sell) commodities ranked most-top first. Distinguishes from sibling 'scan_bottoms' for bottoms and 'pitch' for counts.

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?

Explicitly says when to use: to get sell signals for the whole universe without picking a symbol. Mentions alternative 'pitch' for count, and implies 'evaluate_symbol' for single symbol. Provides cold start guidance.

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

All commodity-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 uniquely identifiable purpose: evaluate_symbol for single-symbol verdicts, pitch for onboarding, rate for feedback, scan_bottoms and scan_tops for universe scans, and subscribe for subscription management. No two tools overlap in functionality.

Naming Consistency4/5

Most tools follow a verb_noun pattern (evaluate_symbol, scan_bottoms, scan_tops), but three are single verbs (pitch, rate, subscribe). The pattern is mostly consistent and readable, with only minor deviations.

Tool Count5/5

With 6 tools, the set covers all essential actions: introduction, single-symbol analysis, universe scanning (bottoms/tops), subscription, and feedback. This is well-scoped for the commodity signal domain.

Completeness4/5

The tool surface covers the core workflow (intro, evaluation, scanning, subscription, feedback). Minor gaps exist, such as a way to filter or request additional symbol details beyond the verdict, but the essential CRUD-like lifecycle is present.

Resources