Skip to main content
Glama

SouthPow crypto & market data

buy_tok_1WIN

Paid. 1win Token (1WIN) 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/1WIN.

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

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, the description carries the full burden and does well: it discloses that this is a paid call, the exact price and accepted payment chains, that no account or API key is required, and that failed calls are not charged. It does not describe latency, rate limits, or response shape, but the core commercial and auth behavior is stated.

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-loaded with 'Paid.' then the payload, then the commercial terms, then the endpoint URL — a sensible ordering with no filler sentences. The terse fragments read like a price sheet rather than prose, which is efficient but slightly staccato.

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 price lookup with no output schema, the description states what fields come back (live USD price, 24h change, market-cap rank) plus cost and payment rails, which is close to everything an agent needs to decide and call. The only gap is not pointing at the sibling tool for other tokens.

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 has zero properties, so there is nothing for the description to disambiguate. Baseline is 4 for a parameterless tool; the description correctly implies no arguments are needed beyond invoking it.

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 resource and verb-equivalent action: the live USD price, 24h change and market-cap rank for the 1WIN token, so the payload is unambiguous. It is distinguishable from the hundreds of sibling buy_tok_* endpoints only by the token symbol embedded in the name, which the description does restate explicitly, but it never says 'for other tokens use the corresponding buy_tok_*' tool.

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 description conveys the purchase terms (paid, $0.05 USDC on Base or Solana, no account, no API key, failures not charged), which tells an agent this is a usable paid lookup without setup. However, it gives no explicit when-to-use guidance versus alternatives such as the near-identically named buy_tok_WIN or the generic buy_crypto_price, leaving disambiguation to inference.

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