Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PEARL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact cost and payment chains, that authentication is unnecessary, and that failures are free. That is meaningful behavioral context an agent needs before invoking. It stops short of describing response format or rate limits/payment failure handling.

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 core result (price, 24h change, rank), then cost, then auth, then endpoint — a sensible priority order with no filler. The telegraphic sentence fragments are efficient, though the trailing bare URL is slightly abrupt.

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 no annotations, so the description must stand alone, and it covers what data is returned, the price, the payment rails, and the no-auth/no-charge-failure policy. It does not specify the response shape or how a caller pays (wallet flow), which leaves a gap for a paid tool with nothing else documenting it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 would normally apply. However, the description does not clarify that the asset is fixed and no symbol argument is accepted, which matters next to hundreds of sibling per-token tools; a 3 reflects that small missed opportunity rather than any misinformation.

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?

Names the specific resource (Pearl/PEARL live USD price) and enumerates exactly what is returned: 24h change and market-cap rank. That is a clear verb-and-resource statement. It does not differentiate itself from the many sibling per-asset price tools (e.g. buy_tok_PEAR, buy_crypto_price), so an agent cannot tell from the description alone why this one rather than another.

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?

Provides operative context — no account or API key needed, failed calls are not charged, price is $0.01 USDC on Base or Solana — which tells an agent it can call this without setup. But there is no explicit when-to-use/when-not guidance or routing to alternatives such as buy_crypto_price or the other PEARL-adjacent tools; usage is only implied by the asset 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