Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PPT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 paid nature, the exact price and accepted payment chains (Base or Solana), absence of auth requirements, and a failure-billing policy that protects the caller. It omits data freshness/latency (is the price real-time or cached?) and any rate-limit or error semantics beyond non-billing, which keeps it below a 5.

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?

About 30 words in telegram style, front-loaded with the payment flag and then the payload description, so the most decision-critical fact (it costs money) comes first. Every clause carries information (price, chains, no auth, no charge on failure). The trailing raw vendor URL is marginally useful and the fragments are slightly clipped, but there is no filler.

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?

For a zero-parameter, no-output-schema tool, the description must supply the return contract, and it does name the three returned values plus cost and failure policy. It stops short of stating the response shape (JSON fields, units, precision, timestamp) or freshness, which an agent needs to use the result correctly when there is no output schema to lean on.

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 no parameter meaning to add and the baseline of 4 applies. The description correctly implies the asset is fixed by the tool itself rather than passed in, which is the only semantic point worth conveying here.

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 verb and resource: returns the live USD price, 24h change and market-cap rank for Populous (PPT). The ticker is explicit and the returned fields are named, so what it does is unambiguous. It does not explain why it exists alongside sibling token/price tools such as buy_crypto_price or the buy_coin_* family, so sibling differentiation is left to the name.

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?

There is no explicit when-to-use/when-not or named alternative, so the agent must infer selection from the ticker in the name. However the description does supply decision-relevant preconditions — it is a paid call at $0.01 USDC, requires no account or API key, and failed calls are not charged — which lets an agent judge whether to spend on it. That is implied guidance rather than routing 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