Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CRCLON

Paid. Circle Internet Group (Ondo Tokenized Stock) (CRCLON) 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/CRCLON.

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_CRCLON"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of rate limits, latency, or the concrete response shape, but the commercial and auth behaviour — the parts an agent would otherwise get wrong — are covered.

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?

Front-loaded with the charge warning ('Paid.') before the payload description, which is the right ordering for a paid tool. Dense but every clause carries information — cost, chains, auth, billing policy. The telegraphic fragment style is slightly abrupt but no sentence is wasted.

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, single-asset price endpoint with no output schema and no annotations, the description covers what comes back (price, 24h change, rank), what it costs, how to pay, and that no credentials are needed. The main remaining gap is the exact response structure, but with no output schema declared and the fields already named, an agent has enough to call it correctly.

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, so the schema leaves nothing ambiguous and there is no parameter semantics to compensate for. The description correctly adds no parameter prose, which is the right call here.

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?

Names a specific verb and resource — live USD price for Circle Internet Group (Ondo Tokenized Stock), ticker CRCLON — and enumerates the returned fields (price, 24h change, market-cap rank). An agent can distinguish this from the many buy_tok_* siblings, including near-neighbours like buy_tok_CRCL, buy_tok_CRCLX and buy_tok_CRCLB, because the underlying asset is spelled out in the description itself.

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?

Usage is implied: this is the price-lookup call for one specific tokenized equity. There is no explicit when-to-use statement, no exclusion naming what to call for the non-tokenized Circle equity, and no guidance on whether to prefer a cheaper generic crypto tool first. Adequate, but the agent must infer the routing.

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