coin-signal

by com.airblockfz

Check your subscription status & terms (FREE), or activate the monthly plan: call with activate:true to receive the $50 x402 payment challenge, sign it, and retry — that buys 30 days of unlimited calls and returns your X-SUB-KEY token (pass it as a header to skip per-call payment). Until you subscribe, signal calls are $0.01 each (6-day trial from your first paid call). Optionally pass your ERC-8004 agentId to link it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agentId`	No	Optional ERC-8004 agent id to link to this subscription.
`activate`	No	true = request the $50 subscription payment challenge (402) to sign & retry.

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses the activation process (402 challenge, signing, retry), the resulting token (X-SUB-KEY), and the trial/per-call cost structure. It lacks explicit mention that activation is a write operation incurring charges, but the payment context is implied.

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?

The description is dense but efficient, covering status check and activation in the first sentence. Every sentence adds value, though the length could be slightly reduced for clarity. It is front-loaded with the core purpose.

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?

While activation flow and token return are well described, the description omits what the status check returns (e.g., plan details, expiration). No output schema exists, so this is a gap. Error cases or already-subscribed behavior are not mentioned. Adequate but incomplete.

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 coverage is 100%. The description adds meaning beyond the schema: explains that activate triggers a payment challenge, and agentId links the subscription. It could elaborate more on agentId's purpose, but the extra context is valuable.

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 two distinct actions: checking subscription status (FREE) and activating the monthly plan via activate:true. It distinguishes itself from sibling analysis tools (evaluate_symbol, pitch, etc.) as a billing/subscription management tool.

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?

The description explains exactly when to use each mode: call without activate to check status, call with activate:true to start the payment challenge. It provides step-by-step guidance (sign challenge, retry) and explains the consequence of not subscribing (per-call fee).

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

All coin-signal tools Inspect

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

Need Help?