Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN56

Paid. Gradients (SN56) 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/SN56.

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

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 no annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted chains, that no auth is needed, that failed calls are not charged, and even the endpoint URL. Missing only rate limits, latency, or caching behavior, which are secondary for a zero-parameter price lookup.

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, no filler: what it returns, cost, chains, auth, failure billing, endpoint. The most decision-relevant facts (payment and no-key requirement) follow immediately after the one-line purpose.

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 tool, the description covers everything an agent needs: the returned fields, the price, payment chains, absence of auth, and non-billing on failure. Nothing required to invoke it correctly is missing.

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 no parameters, so baseline is 4; the description correctly implies all specificity (token, quote currency, chains) is baked into the tool rather than passed as arguments. No further parameter meaning is needed.

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 the exact resource ('Gradients (SN56)') and enumerates the returned data: live USD price, 24h change, and market-cap rank. That distinguishes it from the many sibling buy_tok_SN* variants without opening a schema, though it never uses an explicit verb like 'Returns' so the action is inferred rather than stated.

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?

It gives cost and prerequisite context ($0.01 USDC on Base or Solana, no account, no API key) which helps an agent decide it is callable, but never says when to prefer it over siblings like buy_crypto_price or buy_coin_* for the same asset. Usage must be inferred from the token name alone.

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