Skip to main content
Glama

coin-signal

by com.airblockfz

scan_tops

Scan the market and return coins currently at a top (most overbought / 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 50)
symbolsNoOptional custom symbol list; defaults to a top-coins set

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses payment mechanics ($0.01 per call, x402, trial) and cold start behavior. It lacks details on rate limits or caching but is adequately transparent for a paid API.

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?

Four sentences efficiently cover purpose, payment, and usage guidance. Could be slightly more terse, but no filler.

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

Completeness3/5

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

No output schema exists; description lacks details on the return format (e.g., fields for each coin). Could specify what data is returned besides ranking.

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 covers both parameters with descriptions; the description adds context about default behavior (no symbol needed) and ranking order, complementing 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 scans the market for coins currently at a top (most overbought/sell) and ranks them. This is specific and distinguishes from siblings like scan_bottoms.

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?

Explicitly contrasts with the 'pitch' tool (count versus names) and highlights cold start behavior. Provides payment and trial usage instructions, though it does not cover all sibling tools.

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

All coin-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.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: pitch for introduction, rate for feedback, subscribe for subscription management, evaluate_symbol for single-symbol analysis, and scan_bottoms/scan_tops for market-wide scans. No overlapping functionality.

Naming Consistency4/5

Most tools use a verb or verb_noun pattern with lowercase and underscores where needed (evaluate_symbol, scan_bottoms). pitch, rate, and subscribe are single-word verbs, which is consistent in style. The mix is minor and still readable.

Tool Count5/5

With 6 tools, the set covers the essential actions for a crypto signal service: introduction, single evaluation, market scanning, feedback, and subscription management. This is well-scoped and not overwhelming.

Completeness4/5

The major workflows are covered, including getting signals, scanning the market, and managing subscriptions. A minor gap is the lack of an explicit cancellation tool for subscriptions, but the existing tools provide a complete basic surface.

Resources