Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BINK

Paid. Big Dog Fink (BINK) 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/BINK.

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

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 the call is paid ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It does not cover latency, rate limits, or what a partial/failed response looks like, so it falls short of fully transparent.

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?

Compact and front-loaded: the paid flag, then what data is returned, then cost/chain, then access constraints. The raw endpoint URL is arguably redundant for an agent that cannot call URLs directly, but every other fragment adds real information.

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 tool, the description supplies the returned fields (price, 24h change, market-cap rank), the cost and payment chains, and the access model. Missing only secondary details such as data freshness, quote currency assumptions, and error behavior, which keeps it from a 5.

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 the baseline is 4 and there is nothing parameter-related the description could clarify. The token identifier is baked into the tool name and endpoint rather than exposed as an argument, which is consistent with the empty schema.

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 verb+resource combination: retrieving the live USD price, 24h change, and market-cap rank for Big Dog Fink (BINK). It is clearly a price-fetch tool, but it never explains how it relates to the large family of siblings (e.g. buy_coin_*, buy_crypto_price, other buy_tok_* entries), so an agent must infer that this is the per-token variant.

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 by the token-specific name and the enumerated data fields, but there is no explicit when-to-use guidance, no mention of when to prefer buy_crypto_price or a buy_coin_* sibling, and no statement about freshness or caching limits. The payment mechanics are documented, but routing guidance between alternatives is absent.

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