Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN4

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 behavioral burden and does so well: it discloses the price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the last being a genuinely useful refund policy. What it omits is the payment mechanics (how the USDC charge is actually triggered) and rate limit or latency 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-loading 'Paid.' before anything else is the right call for a purchase tool, and the rest is dense and waste-free. The single line does pack price, output fields, payment rails, auth, refund policy and URL together, which reads as a somewhat clipped telegraphic list rather than prose, but nothing is redundant.

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, single-resource paid fetch with no annotations or output schema, the description covers nearly everything an agent needs to decide and act: what it returns, what it costs, where to pay, and that there is no auth step. The remaining gap is the transaction flow — how invoking the tool results in a USDC charge — which matters for a paid endpoint with no annotation support.

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 input schema is empty, so there are no parameters to explain and the baseline of 4 applies. The description usefully reinforces that the token is fixed in the endpoint itself rather than selectable, which prevents an agent from searching for a symbol argument.

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 and scope: live USD price, 24h change and market-cap rank for Targon (SN4), including the crucial mapping of the ticker SN4 to the project name Targon. That distinguishes it cleanly from the hundreds of sibling buy_tok_* variants, and it compensates for the absent output schema by naming the fields returned.

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: the agent infers it should call this when it needs SN4 pricing. There is no comparison to adjacent siblings such as buy_crypto_price or buy_coin_TAO, and no statement of when NOT to use it (e.g., when a cheaper general price endpoint covers the need). The payment-model guidance is present but is not the same as 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