Skip to main content
Glama

SouthPow crypto & market data

buy_tok_YELLOW

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 whole behavioral burden, and it does disclose several important traits: this is a paid call, costs $0.05 USDC, is payable on Base or Solana, requires no credentials, and failed calls are not charged. However, it does not explain how payment is actually settled given there are zero parameters, nor does it mention rate limits, latency, or whether the $0.05 is per call or per session.

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?

Roughly four short clauses, front-loaded with the paid flag and the data payload, then pricing, then access terms, then the endpoint URL. No filler sentences; every clause adds a fact an agent would otherwise have to guess.

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 is returned, what it costs, and how to access it. The one real gap is the mechanics of payment settlement and the response shape, which matter for a metered endpoint but are partially implied by the URL.

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 input schema has no parameters, so the baseline of 4 applies. There is nothing for the description to clarify regarding arguments, and the token is baked into the tool identity.

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 exact resource (Yellow / YELLOW) and enumerates the returned data: live USD price, 24h change, and market-cap rank. That is enough to separate it from the hundreds of buy_tok_* siblings by token symbol, though it never explicitly contrasts itself with near-duplicates like buy_coin_YELLOW or buy_crypto_price.

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?

It states the access conditions ('No account, no API key') but gives no guidance on when to pick this paid per-token endpoint over the apparently overlapping buy_coin_YELLOW or the generic buy_crypto_price. The agent must infer selection purely from the tool name.

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