Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CRCLX

Paid. Circle xStock (CRCLX) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CRCLX.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buy_tok_CRCLX"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does reasonably well: it discloses the price ($0.05 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and the failure policy ('failed calls not charged'). It does not mention rate limits, latency, or response encoding, so it stops short of a 5.

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?

It is front-loaded with 'Paid.' then the payload, then the commercial terms, which is the right order for an agent deciding whether to spend money. Every sentence carries information; the raw endpoint URL is arguably redundant but harmless and useful for paid x402-style calls.

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 zero-parameter, no-output-schema paid lookup, the definition covers what is returned, what it costs, how to pay, and what happens on failure. The main omission is output shape (field names/format), which matters slightly because there is no output schema to fall back on.

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?

The tool takes zero parameters, which is the baseline-4 case. The description correctly implies a parameterless single-asset lookup, so an agent will not look for a symbol or date argument that does not exist.

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 concrete verb and resource: it returns the live USD price, 24h change and market-cap rank for Circle xStock (CRCLX). An agent knows exactly what data comes back. It does not, however, distinguish itself from the many near-identical siblings such as buy_tok_CRCL, buy_tok_CRCLB, buy_tok_CRCLON and buy_tok_RCRCL, which is a real ambiguity in this catalogue.

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

Usage Guidelines3/5

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

The word 'Paid.' and the stated cost give an implicit precondition for use, and the no-account/no-API-key note tells the agent it can call without setup. There is no explicit when-to-use versus when-not, and no pointer to a cheaper alternative (e.g. buy_crypto_price) if the agent only needs generic price data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources