Skip to main content
Glama

coin-signal

by com.airblockfz

evaluate_symbol

Return the bottom/top verdict for one crypto symbol (e.g. BTC-USD). zone = strong_buy|buy|sell|neutral, score -100..+100 (bottom>0, top<0), with daily/weekly/monthly breakdown. Informational only, not financial advice. 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
symbolYesCrypto symbol, e.g. BTC-USD, ETH-USD, or BTCUSDT

TDQS

A4.6/5.0
Behavior4/5

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

Without annotations, description adds critical behavioral context: payment required, trial, retry with header, informational disclaimer. Could mention data freshness or rate limits, but current detail is strong.

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 somewhat lengthy but front-loaded with purpose and format, then payment details, then sibling distinction. Every sentence adds value; could be slightly more concise.

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?

Given no annotations and no output schema, description fully covers purpose, output format, pricing, trial, retry logic, and differentiation from free tool. No gaps for typical use.

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?

Single parameter 'symbol' with 100% schema coverage; description reinforces with examples (BTC-USD, ETH-USD, BTCUSDT), adding value beyond 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?

Clearly states it returns bottom/top verdict for one crypto symbol with zone, score, and breakdown. Distinguishes from sibling 'pitch' tool which is free but limited to showcase symbol.

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 tells when to use this tool (any symbol) versus the free pitch tool (showcase only). Provides payment instructions and retry behavior on 402 challenge.

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