Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JPYSC

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

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

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 carries the full burden and does substantial work: it discloses that the call is paid, the exact price ($0.05 USDC), accepted payment chains, that no account or API key is required, and the failure billing policy. What it omits is return shape detail beyond the three named fields and any latency or rate-limit 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?

Roughly three short sentences, front-loaded with the paid/cost facts before the data description. The 'JPYSC (JPYSC)' duplication is dead weight and the raw endpoint URL is of marginal value to an agent, but nothing is padded.

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 lookup, the description covers cost, payment rails, auth requirements, failure billing, and the returned fields — the things an agent needs before spending money. The lack of output schema means some return-format detail is missing, but the described fields partially compensate.

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 and the description correctly offers no parameter guidance, which matches the empty schema. Baseline 4 applies since there is nothing further to disambiguate.

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 the resource (JPYSC) and the exact payload on offer: live USD price, 24h change and market-cap rank, with 'Paid' signaling this is a purchase wrapper. It does not distinguish itself from near-identical siblings such as buy_tok_JPYC or buy_crypto_price beyond the ticker symbol, which is already encoded in the tool name.

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?

There are usable preconditions ('No account, no API key', '$0.05 USDC on Base or Solana', 'Failed calls not charged'), so an agent knows what it takes to invoke the call. However, there is no explicit when-to-use or when-not-to-use guidance relative to the ~1000 buy_tok_* siblings or the generic buy_crypto_price tool, so selection must be inferred from the ticker alone.

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