Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KOGE

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

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

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, the exact price and payable chains, that no credentials are required, that failed calls are free, and the underlying endpoint URL. It does not mention rate limits, latency, or what a failure response looks like, which keeps it short of a 5.

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?

The description is front-loaded with the 'Paid' marker and then packs scope, contents, cost, auth, and endpoint into a few dense fragments. Every clause carries information, though the telegraphic style and raw URL appended at the end read more like a listing than a structured sentence.

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, single-value lookup with no output schema, the description supplies the returned fields and the payment/auth model, which is enough for an agent to invoke it correctly. The remaining gap is the response shape and error behavior, which are not covered by an output schema here.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The fixed KOGE scope is unambiguous from the name and description, so no additional parameter meaning is needed.

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?

The description names the specific resource (KOGE token price) and enumerates exactly what the response contains: live USD price, 24h change, and market-cap rank. It is clearly a read of one token's market data, but it never distinguishes itself from near-identical siblings like buy_crypto_price or the buy_coin_* family, so an agent must infer the choice from the token symbol alone.

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?

It establishes the commercial context up front ('Paid', '$0.05 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged'), which tells an agent the prerequisites for invoking it. However, there is no explicit when-to-use or when-not-to-use guidance relative to the many other price tools, and no indication of data freshness or caching that would let an agent pick this over an alternative.

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