Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JPYC

Paid. JPY Coin (JPYC) 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/JPYC.

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

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?

No annotations are supplied, so the description carries the full burden and does so well: it discloses the cost and payment rails ($0.05 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged — non-obvious commercial behavior an agent needs. Remaining gaps are freshness semantics ('live' is undefined) and any rate limit or retry behavior.

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-loads 'Paid.' so cost is the first thing seen, then payload, then access terms, then endpoint — a sensible ordering with almost no filler. The bare trailing 'URL https://...' is slightly abrupt but still earns its place for an HTTP-priced tool.

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?

With no output schema, the description must describe the return surface, and it names the three returned fields (USD price, 24h change, market-cap rank). Combined with cost, payment rails, and failure-charging policy, an agent has enough to decide and call. It stops short of output shape/unit details or freshness windows.

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 the baseline of 4 applies. The description correctly signals a no-argument call by naming the asset inline.

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 resource and payload: 'JPY Coin (JPYC) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back. It does not, however, distinguish itself from the hundreds of sibling buy_coin_* / buy_tok_* price tools, so the tok-vs-coin series boundary is left implicit.

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 by the payload description; there is no explicit 'use this when...' or routing to alternatives such as buy_coin_* or buy_crypto_price. The pricing/access lines ('$0.05 USDC on Base or Solana', 'No account, no API key') effectively communicate when the tool is usable, which raises it above a bare 2.

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