Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GT

Paid. Gate (GT) 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/GT.

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

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 supplied, the description carries the whole burden and does well: it discloses the price and accepted payment chains, that no account or API key is needed, and that failed calls are not charged — real behavioral facts an agent needs before spending money. It stops short of explaining the payment flow itself (how the USDC is submitted) or what the response body 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?

Six short telegraphic fragments, front-loaded with 'Paid.' followed immediately by what the tool returns, then commercial terms. Nearly every clause adds information; the raw URL is the only segment that could arguably be considered reference material rather than guidance.

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 paid endpoint, the description covers purpose, returned fields, cost, payment chains, and failure billing — which is what an agent needs to call it correctly. The only residual gap is sibling differentiation, which is a selection concern rather than a completeness one.

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 an empty object with no properties, so there are no parameters to clarify; the baseline for a zero-parameter tool is 4. The description correctly implies a fixed, no-argument call by giving a literal endpoint URL.

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 verb-equivalent ('Gate (GT) price') and enumerates what is returned: live USD price, 24h change, and market-cap rank. That makes the payload unambiguous. It does not differentiate this from sibling families such as buy_coin_* or buy_crypto_price, so an agent must infer the tok-vs-coin distinction on its own.

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 leading word 'Paid' plus '$0.05 USDC on Base or Solana' is genuine usage context — it tells the agent this call has a cost and should be chosen deliberately. However, there is no explicit statement of when to prefer this over the many buy_coin_* price tools or buy_crypto_price, and no prerequisites are named beyond 'no account, no API key'.

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