Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BCSPX

Paid. Backed CSPX Core S&P 500 (BCSPX) 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/BCSPX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the pay-per-call cost, accepted payment rails (USDC on Base or Solana), the absence of auth requirements, and a meaningful billing guarantee that failed calls are not charged. What is missing is rate limiting, caching/staleness policy, and what an error response looks like, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the paid flag, then the resource, then the returned fields, then cost/auth/billing terms. Every clause carries information an agent needs; nothing is redundant filler, and the trailing endpoint URL is compact.

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, no-annotation tool, the description covers cost, payment, auth, billing on failure, and the three returned data points — enough to call it correctly and predict the payload. It falls short only on response format details and data freshness, which matter slightly given 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, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameter talk and instead spends its words on cost and return content.

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?

States a specific resource (BCSPX, the Backed CSPX Core S&P 500 token) and exactly what is returned: live USD price, 24h change, and market-cap rank. Against hundreds of near-identical buy_tok_* siblings, the token identity is the differentiator and it is stated unambiguously in the first sentence.

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?

Gives useful preconditions — it is paid, costs $0.01 USDC on Base or Solana, and requires no account or API key — which tells an agent whether it can be called at all. It never says when to prefer this over the generic buy_crypto_price or a category tool like buy_cp_majors, nor does it state any exclusion or freshness assumption, so the when-to-use routing is only implied by the token name.

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