Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CORE

Paid. Core (CORE) 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/CORE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the paid model, exact price, accepted chains and currency, that no credentials are required, that failed calls are not charged, and the underlying endpoint URL. What it omits is the response format/shape and any latency or rate-limit behavior.

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?

It is a short, front-loaded block: asset and returned fields first, then cost and payment rails, then the URL. Every sentence carries information, though the ordering scatters the payment facts across three fragments rather than grouping them into one cost statement.

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 lookup, the description supplies what an agent needs to decide and pay: what data comes back, what it costs, on which chains, and the raw endpoint. Only the exact response serialization is left unspecified, which is a minor gap given the fields are enumerated.

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, and the description correctly adds no spurious argument guidance.

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 names a specific asset (Core / CORE) and the exact data returned: live USD price, 24h change, and market-cap rank. That is far more than a restatement of the name and lets an agent identify the operation. It does not explicitly distinguish itself from near-neighbours such as buy_crypto_price or buy_coin_CORECHAIN, so it stops short of a 5.

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: an agent can infer this is the tool for CORE spot data, and the payment terms ($0.01 USDC on Base or Solana, no account, no API key) set the cost context. There is no statement of when NOT to use it, nor any pointer to free or alternative price tools among the many siblings.

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