Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN14

Paid. Cacheon (SN14) 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/SN14.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 a decent job: it discloses pricing and accepted payment chains, the no-auth requirement, and the failed-call refund policy — all behavior an agent would otherwise have to guess. It stops short of stating rate limits, data freshness/cadence, or response format, so the safety and operational profile is only partly covered.

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 telegraphic and front-loaded: 'Paid.' then what the data is, then cost, then payment rails, then the refund policy, then the endpoint URL. Nearly every fragment earns its place, though the sentence is somewhat choppy and the trailing raw URL is of marginal use to an agent that cannot call it directly.

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, output-schema-less price lookup, the description supplies what matters: the exact asset identity (Cacheon, SN14), the three returned metrics, cost, payment options, and failure policy. It lacks only secondary details like response structure or update frequency, which are minor for a fixed-field price endpoint.

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 implies the call is fully self-contained with the asset 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 names the resource precisely ('Cacheon (SN14) price') and enumerates the returned fields: live USD price, 24h change, market-cap rank. It is clearly distinguishable from generic siblings like buy_crypto_price, but it does not explicitly state a verb or contrast itself with the many other buy_tok_SN* subnet tools it sits beside.

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 conveys practical usage context — it is a paid call, costs $0.01 USDC on Base or Solana, requires no account or API key, and failures are not charged — which tells the agent it can call it without setup. However, there is no explicit when-to-use guidance versus alternatives such as buy_tok_SN19 or buy_crypto_price, and no exclusions or prerequisites beyond payment.

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