Skip to main content
Glama

SouthPow crypto & market data

buy_tok_P33

Paid. Pharaoh Liquid Staking Token (P33) 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/P33.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the paid model ($0.05 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It stops short of rate limits, latency/freshness, and what the response body looks like, which for a metered endpoint would matter.

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?

Front-loaded with the payment flag, then the resource and its fields, then the commercial terms, then the URL. Six short clauses, each carrying a distinct fact, with no filler or restatement of the tool name.

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 call, the definition covers what is returned, what it costs, on which chains, and the failure-billing policy. The main remaining gap is response shape and data freshness, but an agent has enough to decide and invoke correctly.

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; baseline 4 applies. The token identity is baked into the tool rather than passed as an argument, and the description makes that clear.

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 specific resource ('Pharaoh Liquid Staking Token (P33) price') and enumerates the payload: live USD price, 24h change, market-cap rank. That is enough to tell it apart from the hundreds of sibling buy_tok_* entries by token, though it never distinguishes itself from adjacent families like buy_coin_* 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 Guidelines3/5

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

Usage is implied rather than stated: an agent infers 'call this when you need the P33 price'. There is no explicit when-not, no named alternative (e.g. buy_crypto_price for a generic quote), and no guidance on caching or repeat calls despite a per-call charge.

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