Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN53

Paid. EfficientFrontier (SN53) 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/SN53.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full behavioral load, and it does disclose genuinely useful facts: it is a paid call, the exact cost ($0.01 USDC on Base or Solana), no account or API key required, and that failed calls are not charged. It does not disclose rate limits, latency, or response/error format beyond the failure-charging policy, so it is solid but not complete.

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', then states the payload, then cost and payment rails, then guarantees, then the endpoint. Every clause carries information; the only near-redundant element is the raw URL, which is arguably useful for a direct paid endpoint.

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?

Zero parameters and no output schema keep complexity low, and the description still covers what is returned, the price, the payment method, and the failure policy. The remaining gap is response shape and freshness/rate-limit guarantees, which matters somewhat for a live-price tool but is not critical.

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 of 4 applies. The description adds no parameter meaning because none exists, but it also creates no ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (EfficientFrontier / subnet SN53), states exactly what the caller gets ('live USD price, 24h change and market-cap rank'), and the token identifier in the name plus the explicit symbol in the description is what separates it from the hundreds of buy_tok_* siblings. An agent can pick this one out of the family without opening anything else.

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 infers 'call this when you want the SN53 price'. There is no explicit when-to-use statement and no mention of an alternative such as buy_crypto_price or the other subnet token tools, so the routing decision is left to the agent's inference.

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