Skip to main content
Glama

SouthPow crypto & market data

buy_tok_INIT

Paid. Initia (INIT) 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/INIT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses the paid nature, the exact cost and accepted payment rails (USDC on Base or Solana), the absence of auth requirements, and the important failure semantic that failed calls are not charged. It stops short of rate limits, latency, or caching, but the commercial and auth behaviors an agent most needs before spending money are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one word that matters most ('Paid'), then the payload, then cost, then access terms, then the raw URL. Six short fragments with no filler; every clause carries distinct decision-relevant information.

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 price endpoint, listing the returned fields inline substitutes adequately for an output schema. Adding expected response shape or update freshness would close the remaining gap, but nothing essential to a correct invocation is missing.

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, which is the baseline-4 case — there is nothing for the description to disambiguate. The ticker is baked into the endpoint, and the description correctly conveys that no per-call input is required.

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 asset (Initia / INIT) and enumerates the exact returned fields — live USD price, 24h change, market-cap rank — so an agent knows precisely what this endpoint produces. Among hundreds of buy_tok_* siblings the ticker in the title and URL is the only differentiator, and the description does not explicitly say 'this is the INIT variant, use buy_crypto_price for general queries,' which keeps it just short of 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?

'Paid' plus the $0.01 USDC price and 'no account, no API key' give practical preconditions for calling. However, there is no explicit when-to-use vs alternatives guidance — nothing distinguishes it from buy_crypto_price or explains when the market-cap-rank field is the reason to pick this over a cheaper sibling.

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