Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JOE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. Missing are rate limits and whether repeated calls are each billed. Given zero annotation coverage, this is a strong disclosure but not exhaustive.

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?

Six short fragments, front-loaded with the paid flag and the data returned, with cost and prerequisites following. Nothing is padded. Minor deduction for the redundant 'JOE (JOE)' construction and the terse 'Paid.' opener, which reads more like a label than a sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by listing the returned fields. Payment mechanics are unusually well covered. The gap is sibling disambiguation: an agent reading this cannot tell why it would call buy_tok_JOE instead of buy_coin_JOE, which is a completeness problem in a catalog of this size.

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 correctly implies the asset is fixed by the tool name rather than passed as an argument.

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 a specific resource (JOE price) and enumerates the exact payload: live USD price, 24h change, and market-cap rank. That is far beyond a tautology. It loses a point because it never distinguishes itself from the near-identical sibling buy_coin_JOE (or buy_crypto_price), which an agent would have to choose between by name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, and no exclusions. With hundreds of sibling price tools including buy_coin_JOE for the same asset, the absence of any routing guidance is a real gap. Prerequisites ('no account, no API key') are present but that is not when-to-use guidance.

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