Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PORKU

Paid. HoodPork (PORKU) 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/PORKU.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 that the call is paid, the exact price and accepted chains, that no account or API key is needed, and that failed calls are not charged, plus the literal endpoint URL. It stops short of describing the response shape or any rate limits, which leaves a small gap for a zero-annotation tool.

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?

Six short fragments, front-loaded with the most decision-relevant fact ('Paid.') and then purpose, cost, and auth/failure terms. Nothing is padded and no sentence restates the tool name without adding information.

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 call, the description supplies the returned fields inline, the payment model, and the failure-charging policy, which is enough to invoke it correctly. It would be complete at 5 if it sketched the response format or latency, since no output schema exists to cover that.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent argument detail the schema cannot accept.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (HoodPork / PORKU) and exactly what it returns: live USD price, 24h change and market-cap rank. The ticker-to-name mapping plus the explicit field list lets an agent distinguish it from the hundreds of sibling buy_tok_* price tools without opening a schema.

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?

The leading 'Paid.' and the '$0.01 USDC on Base or Solana' line tell the agent this is a costed call, which is useful selection context. However, it never says when to prefer buy_crypto_price or another sibling, nor any exclusion condition (e.g., stale/unsupported tickers). Usage is implied rather than instructed.

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