Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CRCLB

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With zero annotations, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged — three things an agent cannot infer from an empty schema. It stops short of describing response shape, data freshness, or rate limits, which leaves a modest gap.

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?

Six short fragments, front-loaded with 'Paid.' so cost is known before anything else, then identity, payload, price, auth, refund policy, endpoint. Nothing is redundant for a paid endpoint where cost and payment chain are decision-critical.

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 zero-parameter, no-output-schema price lookup, the description covers identity, returned fields, cost, payment chains, authentication, failure billing, and the endpoint URL. An agent has everything needed to call it and to predict what it costs, with no structural fields left to carry undisclosed meaning.

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 baseline is 4; nothing in the input schema needs explanation. The description correctly implies no arguments are required to get this specific ticker's price.

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 the exact resource (Circle Internet Group bStocks Tokenized Stock, ticker CRCLB) and the exact payload returned: live USD price, 24h change, and market-cap rank. The asset-class label 'bStocks Tokenized Stock' meaningfully separates it from the mass of buy_coin_* and buy_tok_* crypto siblings whose symbol alone would not tell an agent this is a tokenized equity, though it does not name any specific sibling.

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 by the payload description ('price') rather than stated: there is no explicit when-to-use, no exclusion, and no pointer to an alternative such as buy_crypto_price or the related buy_tok_CRCL/CRCLX/CRCLON tickers. The payment and auth notes give practical context for deciding whether it can be called, but not when it should be.

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