Skip to main content
Glama

SouthPow crypto & market data

buy_tok_A

Paid. Vaulta (A) 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/A.

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

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, the description carries the full burden and does well: it discloses the $0.01 USDC cost, the two accepted payment chains (Base, Solana), that no account or API key is required, and that failed calls are not charged. Missing only rate limits and any note on data freshness/latency behind 'live'.

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?

Front-loads 'Paid.' before anything else, then purpose, then price/auth terms, then the URL. Nearly every clause carries information an agent needs. The explicit 'URL ...' line is slightly redundant with the name, but it is actionable for a paid HTTP call.

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 data tool, the description covers cost, auth, failure policy, and the fields returned — enough to call it correctly and to reason about spend. Only response shape/format and refresh cadence are unstated.

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 and there is no schema meaning the description needs to compensate for. Nothing about invocation is left ambiguous — the asset 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?

Names the exact resource (Vaulta / A) and enumerates the returned fields: live USD price, 24h change, market-cap rank. The 'Paid.' prefix and a concrete endpoint make the operation unambiguous. It does not, however, distinguish itself from the many sibling price tools such as buy_coin_* or buy_crypto_price, so an agent must infer the boundary.

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 needing A's spot price is the obvious caller. There is no explicit when-not guidance and no named alternative (e.g., buy_crypto_price or the buy_coin_* family), despite those being close substitutes in the sibling list.

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