Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN120

Paid. affine (SN120) 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/SN120.

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

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 provided, the description does the heavy lifting well: it discloses that the call is paid, the exact cost, the accepted payment networks, that no authentication is required, and that failed calls are not charged — all non-obvious behavioral traits for a metered tool. It stops short of describing the response payload shape or what an error response looks like, which matters since there is no output schema.

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 short and front-loaded: the paid status and payload come first, followed by price, prerequisites, and endpoint. The telegraphic 'affine (SN120) price:' fragment is slightly clipped, and the raw URL at the end is useful mainly for agents that need the endpoint but reads as an appendage.

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, metered endpoint, the description covers the important unknowns: what is returned, what it costs, how to pay, and that failures are free. The remaining gap is response format and error semantics, which an agent would want before spending USDC on a call.

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 and the baseline applies. The description correctly implies the token is fixed by the endpoint (SN120), which is the right thing to convey for a parameterless call.

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 and its payload: 'affine (SN120) price: live USD price, 24h change and market-cap rank', which lets an agent distinguish it from the ~900 sibling buy_tok_* tools tied to other tickers. It does not explicitly state that the SN120 suffix is the only thing separating it from buy_tok_SN107/S N110/etc., so differentiation is inferred from the token name rather than called out.

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 context is present but commercial rather than selectional: it discloses the $0.05 USDC price, payment chains (Base or Solana), and that no account or API key is needed, which is genuinely useful before calling. It never says when an agent should prefer this paid per-token endpoint over alternatives such as buy_crypto_price or the other buy_tok_* variants, so the when-to-use decision is only implied.

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