Skip to main content
Glama
Sign In

Stelar Signals

by io.github.StelarDigital
OverviewDiscussionsAdmin

Market-regime classification (paid: $0.03/call via x402)

regime
Read-only

PAID PER CALL ($0.03 USDC on Base via x402). Market regime (chop / trend_up / trend_down / high_vol) plus a grid-suitability verdict, computed from live 24h market structure. 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": "regime"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already indicate a safe read, and the description adds meaningful behavior beyond that: the $0.03 USDC x402 payment requirement and the fact that unpaid calls return payment terms instead of data. This is valuable context not present in the schema or annotations.

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?

The description is three tight sentences: payment warning first, then output definition and data basis, then unpaid-call behavior. No filler or redundant schema text.

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?

For a single-parameter read-only classification call, the description covers the output categories, the computation basis, the cost, and the no-payment fallback. There is no output schema, but the semantic outputs are stated well enough to interpret the response.

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?

Asset is fully documented in the schema with an enum and description (100% coverage), so the description adds no parameter information. This matches the baseline for high schema coverage.

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 names a specific resource (market regime classification), lists the exact output categories (chop / trend_up / trend_down / high_vol), and adds a grid-suitability verdict, so an agent knows what the tool does. It does not differentiate from sibling crypto_regime, so not a 5.

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?

There is no guidance on when to choose this tool over crypto_regime or related risk/sentiment tools, and no exclusions or alternative routing. The only context is that it uses live 24h market structure, which is implied rather than stated as a usage condition.

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