Skip to main content
Glama
Sign In

Stelar Signals

by io.github.StelarDigital
OverviewDiscussionsAdmin

Crypto price + change snapshot (paid: $0.005/call via x402)

price
Read-only

PAID PER CALL ($0.005 USDC on Base via x402). Current price, 24h/7d change, and a simple signal for a major crypto asset. Unpaid calls return the exact x402 payment terms.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset": "<asset>"
    },
    "name": "price"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive, so the bar is lower. The description adds valuable behavioral context beyond the annotations: the exact cost per call, the payment mechanism (x402 on Base), and the fallback behavior for unpaid calls.

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?

Three short sentences, with the critical paid-per-call warning front-loaded. Every sentence earns its place and there is no filler.

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?

For a single-parameter, read-only snapshot tool, the description covers output content and payment behavior sufficiently, and no output schema exists to complicate expectations. It is slightly vague about what the 'simple signal' actually is, but this does not block correct invocation.

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% and the lone asset parameter is fully documented with an enum. The description adds no real semantic detail beyond what the schema already provides, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns current price, 24h/7d change, and a simple signal for a major crypto asset, so the core purpose is unmistakable. It does not explicitly differentiate this from the sibling pricecheck, but the resource and outputs are specific enough for an agent to understand what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description communicates that calls are paid and that unpaid calls return x402 payment terms, but it gives no guidance on when to choose this tool over siblings like pricecheck or crypto_regime. No exclusions, conditions, or alternative selection criteria are provided.

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

All Stelar Signals toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources