Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN75

Paid. Hippius (SN75) 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/SN75.

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

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 burden and does well: it discloses cost, accepted payment rails, that no authentication is needed, and that failed calls are not charged — a meaningful billing-safety guarantee. It stops short of stating rate limits, latency, or what a partial/error response looks like.

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?

Very short and front-loaded: payment status first, then payload, then price/rails, then trust guarantees, then URL. Sentence fragments are efficient rather than confusing, though 'Paid.' alone is a slightly abrupt opener.

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 tool the description covers what an agent needs to decide and call: what it returns, what it costs, how to pay, that no key is required, and that failures are free. Only the exact response shape and error semantics are left unspecified, which is minor given no output schema exists.

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 surface to explain and the baseline is 4. The description correctly implies the call is fully specified by the fixed asset (SN75) 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?

States a specific resource (Hippius / SN75) and enumerates the exact payload: live USD price, 24h change, and market-cap rank. An agent can tell this is the SN75 subnet-token price feed rather than one of the many sibling buy_tok_SN* endpoints. It never explicitly contrasts itself with those siblings, which keeps it from 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?

Conveys that this is a paid endpoint ($0.05 USDC on Base or Solana) with no account or API key required, which is real usage context. However, it gives no guidance on when to prefer this over alternatives such as buy_crypto_price or a different subnet tool, and no exclusions or preconditions 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