Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PEAR

Paid. Pear Protocol (PEAR) 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/PEAR.

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

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 full burden and does well: it discloses the $0.01 USDC cost, accepted payment rails (Base or Solana), absence of auth requirements, and the failure-billing policy. It stops short of stating data freshness/refresh frequency or latency beyond the word 'live'.

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?

Four short sentences, front-loaded with the paid flag and the data returned, with cost and payment details following. No repetition, though the telegraphic fragments ('Paid.') read more like ad copy than documentation.

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-param, no-output-schema tool the description covers return fields, cost, payment, auth, and failure policy — enough to call correctly. The only gap is the lack of a pointer telling the agent how this differs from the hundreds of sibling price tools.

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 the schema offers nothing to explain and baseline is 4. The description adds the endpoint URL, which is the only additional calling context an agent could need.

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: PEAR Protocol live USD price, 24h change, and market-cap rank, and notes it is a paid call. An agent can tell what it returns without opening the (empty) schema. It does not distinguish itself from near-identical siblings such as buy_coin_PEARL or other buy_tok_* price endpoints.

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?

Says no account or API key is needed and that failed calls are not charged, which informs the decision to call. However it never states when to prefer this over the parallel buy_coin_* / buy_tok_* price tools, so the agent must infer selection from the ticker alone.

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