Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MEME

Paid. MEMETOON (MEME) 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/MEME.

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

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 so well for a zero-param tool: it discloses that the call is paid, the exact cost and accepted chains ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only finer behavior such as latency, rate limits, or response encoding.

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-loaded with the decisive fact ('Paid.') followed by payload, price, payment chain, auth requirement, failure policy, and endpoint in six telegraphic fragments. Nothing is redundant, though the endpoint URL is of marginal use to an agent that already has the tool bound and the style borders on note-form.

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 lookup, the description supplies the returned fields, the payment model, accepted chains, and billing behavior on failure — essentially everything an agent needs before spending money. Only the concrete response shape (e.g. raw JSON structure) is left unspecified.

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 schema has zero parameters with 100% coverage, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly focuses on cost, chain, and returned fields instead.

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 and payload: 'MEMETOON (MEME) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back. It does not explicitly distinguish itself from the large family of buy_tok_*/buy_coin_* price siblings, though the embedded ticker in the tool name plus the prose makes the subject unambiguous.

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 implied by the described output rather than stated: an agent wanting MEME spot price, 24h change, or rank can select it. There is no explicit when-to-use versus alternatives (e.g. buy_coin_*, buy_crypto_price) and no exclusions or prerequisites beyond 'no account, no API key'.

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