Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TAKE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/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 unusually well on the commercial side: cost ($0.05 USDC), payment chains (Base or Solana), no account or API key, failed calls not charged, and the raw endpoint URL. It still omits whether results are cached/delayed, freshness or rate limits, and what a charged-but-failed response looks like.

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.' and the payload summary before the payment mechanics and URL. The telegraphic fragments ('$0.05 USDC on Base or Solana. No account, no API key.') are efficient, though slightly clipped rather than fully structured prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 endpoint, the description supplies everything needed to invoke it correctly and safely: what data is returned, what it costs, which chains to pay on, that no credentials exist, and that failures are free. Nothing an agent needs before calling is missing.

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 schema offers nothing to interpret and the baseline is 4. The description correctly implies the token is fixed (TAKE) and requires no input, matching 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: fetches the live USD price, 24h change and market-cap rank for the OVERTAKE (TAKE) token. The token symbol in the name and description anchors it against the hundreds of sibling buy_tok_* endpoints, though it never explicitly contrasts itself with buy_crypto_price or the buy_coin_* family.

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 resource ('TAKE price') and the 'Paid' prefix plus the $0.05 charge signal that this is a paid, transactional call, but there is no explicit when-to-use guidance or direction to an alternative price tool among the many siblings. An agent knows what it will get, not why it should pick this over buy_crypto_price.

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