Skip to main content
Glama

commodity-signal

by com.airblockfz

scan_bottoms

Scan the commodity complex snapshot (28 futures: metals, energy, agriculture, livestock) and return commodities currently at a bottom (strongest buy), ranked most-bottom 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 28)

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses payment mechanism ($0.01 per call, first paid call opens trial), retry instructions for 402 challenge, and no account needed. Does not describe error conditions or output format fully, but adequately conveys 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.

Conciseness5/5

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

Five sentences, each adding distinct value: purpose, payment, retry, cold start, contrast with pitch. Front-loaded with the core action. No unnecessary words.

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?

With one optional parameter, no output schema, and no annotations, the description is fairly complete. It explains the tool's action, ranking, payment, and contrasts with a sibling. Could briefly describe output format (e.g., returns list of commodity names or symbols), but 'return commodities' and 'ranked most-bottom first' gives sufficient context.

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?

Schema description coverage is 100% for the single 'limit' parameter. Description adds minimal extra semantics beyond the schema (mentions cold start but not parameter details). Falls at the baseline with no significant added meaning.

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 it scans the commodity complex snapshot and returns commodities at a bottom (strongest buy), ranked most-bottom first. Distinguishes from siblings like 'pitch' and 'scan_tops' by specifying that this names them while pitch tells how many.

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 guidance: best cold start (no need to pick a symbol), contrasts with free 'pitch' tool. Implicitly distinguishes from 'scan_tops' by naming opposite direction. Lacks explicit when-not-to-use for all siblings, but covers main alternatives.

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