Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ID

Paid. SPACE ID (ID) 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/ID.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the paid model, the exact price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits response format and rate-limit details, which keeps it 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.

Conciseness5/5

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

Six short fragments, front-loaded with the single most decision-relevant word ('Paid') and immediately followed by what the call returns. Every sentence earns its place: cost, payment rails, auth requirements, refund policy, endpoint.

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 tool, the description covers what is returned (USD price, 24h change, market-cap rank), what it costs, how to pay, and that failures are free. Only the response encoding/field layout is left unspecified, a minor gap given the tool's simplicity.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description does not invent or misdescribe any input, and the token identity is baked into the endpoint.

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 states a concrete resource and payload: SPACE ID (ID) live USD price, 24h change, and market-cap rank. The token symbol in the tool name plus the explicit 'SPACE ID (ID)' phrasing lets an agent match it to the correct sibling in the large buy_tok_* family, though it never explicitly contrasts itself with buy_crypto_price or the buy_coin_* variants.

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 only implied: 'price: live USD price' tells the agent what it gets, and 'Paid ... $0.05 USDC on Base or Solana' tells it the cost and payment rails. There is no explicit when-to-use versus alternatives (e.g., the buy_coin_ID or buy_crypto_price siblings), and no guidance on how often to call for a 'live' price.

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