Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PURR

Paid. Purr (PURR) 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/PURR.

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

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 zero annotations, the description carries the full burden and does a lot of it: it discloses the paid nature, the exact price ($0.05 USDC), payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It also lists the data fields returned. Missing only operational traits like price freshness/latency and whether payment is per-call authorization flow.

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 and dense: the payload ('price, 24h change, market-cap rank'), the cost, and the auth/failure terms each appear once with no filler. The telegraphic fragments ('Paid.', 'No account, no API key.') are efficient, though 'Paid.' partially duplicates the explicit $0.05 USDC sentence that follows.

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-parameter, no-output-schema price lookup, the description covers what is returned, what it costs, how to pay, auth requirements and failed-call billing, which is essentially everything needed to invoke it. The only gap is data freshness and any rate/throughput limits, minor for a single-value lookup.

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 per the baseline this scores 4. The description adds no parameter meaning because there is nothing to parameterize; all variability (which token) is baked into the tool identity.

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 exactly which resource this returns: the live USD price, 24h change and market-cap rank for Purr (PURR), with the endpoint path confirming the single-token scope. The token symbol in the name plus the URL make it distinguishable from the hundreds of sibling buy_tok_* tools, though the description never explicitly says 'this is PURR only, use another symbol-specific tool otherwise'.

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 only implied: an agent infers it should call this when it wants PURR pricing. There is no explicit when-to-use framing and no mention of alternatives such as buy_crypto_price or buy_coin_* series tools, nor any statement about freshness or how often the price updates. Adequate context but no 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