Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000027

Paid. Tradable LatAm BNPL SSTN (PC0000027) 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/PC0000027.

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

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 supplied, the description does meaningful work: it declares the tool is paid ($0.01 USDC), names payment rails (Base or Solana), states no account/API key is needed, and clarifies failed calls are not charged. These are genuinely useful behavioral facts. It omits latency, rate limits, and result freshness, but the commercial/authentication profile is well covered.

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?

The description is short, front-loaded with the price/purpose, then payment terms, then a docs URL — every clause is functional. It's dense telegraphic phrasing rather than prose, but nothing is wasted.

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 no-parameter single-asset price tool with no output schema, the description provides the returned fields, the payment mechanics, and a reference URL. That is sufficient for an agent to know when and how to call it, though it does not state the response format or freshness window.

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 and no schema gap to compensate for; baseline 4 applies.

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 a specific resource (PC0000027, LatAm BNPL SSTN) and enumerates the returned data: live USD price, 24h change, market-cap rank. It does not explicitly contrast with the many buy_coin_* or buy_tok_* siblings, so it stops short of full disambiguation, but an agent can tell it's a single-asset price lookup.

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 by 'price: live USD price, 24h change and market-cap rank', so an agent knows this is a quote/price tool. There is no explicit when-to-use or when-not, no named alternative (e.g. buy_crypto_price), and no exclusion 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