Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WIN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 declares this is a paid call at $0.05 USDC on Base or Solana, that no account or API key is required, and that failed calls are not charged, plus the raw endpoint URL. It omits rate limits, latency, and whether payment is per-attempt or per-success in the success case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each carrying distinct decision-relevant information – payload, price/chain, access terms – with the paid flag front-loaded. No filler or redundant restatement of the tool name.

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, no-annotation tool, this is nearly sufficient: it names the returned fields, the cost, the settlement chains, and the refund policy. It could add output shape guarantees and any call-frequency limits, but nothing essential is missing for a correct invocation.

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 parameters, so there is no parameter meaning to add; the baseline of 4 applies. Nothing in the schema is left ambiguous for the agent to fill in.

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: WINkLink (WIN) live USD price, 24h change, and market-cap rank. An agent knows exactly what comes back. It does not distinguish itself from the large buy_coin_* family or buy_crypto_price, which appear to serve overlapping price-lookup roles.

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 implied rather than stated: this is the WIN price endpoint, so call it when WIN price data is needed. There is no explicit when-to-use versus buy_coin_*/buy_crypto_price, and no statement of when not to call it or how to chain it with a payment step.

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