Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CRCL

Paid. Circle Internet Group • Robinhood Token (CRCL) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CRCL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, and — importantly — that failed calls are not charged. It omits rate limits, latency expectations, and whether the price source is an aggregator or a single venue.

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?

Front-loads the payment flag ('Paid.'), then identifies the asset, then the returned fields, then the purchase mechanics and failure policy, ending with the endpoint URL. Every clause carries information an agent needs before spending money.

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 endpoint, the description covers cost, payment rails, auth requirements, failure billing, and the shape of the returned data (price, 24h change, market-cap rank). The lack of a precise response schema or currency/rounding convention is a minor residual gap.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description does not waste space restating a nonexistent input schema.

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?

States a concrete verb and resource: live USD price, 24h change, and market-cap rank for the CRCL token, and names the issuer (Circle) and listing (Robinhood Token) to disambiguate the ticker. It does not, however, distinguish itself from the closely-named siblings buy_tok_CRCLB, buy_tok_CRCLON, buy_tok_CRCLX, or buy_tok_RCRCL, which wrap the same underlying asset.

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 explicit when-to-use statement and no mention of alternatives, despite the sibling list containing four other CRCL-derived tickers plus a general buy_crypto_price endpoint. The only usage signal is implicit in the name and the returned fields.

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