Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FP

Paid. Fren Pet (FP) 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/FP.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 that the call is paid, the exact price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. Still missing rate limits, caching/freshness of the price, and any timeout or retry behavior, which matter for an agent deciding whether to re-call.

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?

Six terse clauses, front-loaded with 'Paid.' so the billing fact is the first thing the agent sees, followed by payload, cost, auth posture, failure policy, and URL. Nothing is padded, though the telegraphic style (sentence fragments) is slightly harder to parse than a single well-formed sentence.

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 paid feed, the description supplies what the schema cannot: the returned fields, the price, payment rails, and the failure-billing rule. It leaves return encoding (JSON shape, units, whether 24h change is a percent) unstated, which is the main remaining gap given there is no output schema to fall back 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 the schema cannot be improved upon and the baseline is 4. The description correctly adds no parameter prose, and the token identity is baked into the endpoint URL rather than an argument, which is consistent.

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?

Names the specific asset (Fren Pet, FP) and the exact payload: live USD price, 24h change, market-cap rank. The sibling set is a wall of near-identical buy_tok_* entries, and naming the token plus its endpoint slug is what lets an agent pick this one over buy_tok_<other>. It stops short of 5 because it never contrasts with the generic buy_crypto_price tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Contains no when-to-use or when-not-to-use guidance and no routing to alternatives; an agent must infer from the name that this is the FP-specific feed versus buy_crypto_price or any other buy_tok_* feed. Payment mechanics are stated, but that is operational detail, not selection 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