Skip to main content
Glama

coin-signal

by com.airblockfz

pitch

START HERE — your first call to this agent MUST be pitch (free, no payment). Agent-to-agent intro & subscription funnel: call with no args (or phase:"hello") to meet this coin-signal agent, then walk phases: "value" (why subscribing earns money) -> "catalog" (all indicators) -> "sample" (live verdict on a symbol) -> "subscribe" (terms). Pass interest:false to bow out. Returns structured JSON with a next list of suggested phases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phaseNoFunnel step; default "hello".
symbolNoSymbol for the "sample" phase. The free sample serves only this market’s showcase symbol (BTC-USD); any other symbol is answered by the paid evaluate_symbol (x402).
interestNoSet false at any step to exit politely.

TDQS

A4.5/5.0
Behavior4/5

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

Discloses it's free, no payment, and explains the phase walkthrough and exit via interest:false. No annotations exist, so description carries full burden; adequately covers non-destructive behavior.

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?

Two concise sentences, front-loaded with mandatory instruction, every phrase adds value without redundancy.

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?

Covers funnel sequence, parameters, and return concept of `next` list. Lacks full output structure details but sufficient given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant context beyond schema: describes funnel phases, default phase, symbol usage in sample phase, and interest meaning. Schema coverage is 100%, but description enriches understanding.

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 it's the mandatory first call for an agent-to-agent intro and subscription funnel, specifying phases and distinguishing it from sibling tools like subscribe.

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 tells agents to start here and outlines the funnel sequence. Lacks explicit when-not-to-use comparisons but provides strong contextual guidance.

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