Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AGETH

Paid. Kelp Gain (AGETH) 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/AGETH.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 a solid job: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. Gaps remain on rate limits, latency, and whether the price is a mid/last quote, but the commercial and auth behavior is unusually well surfaced.

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?

Roughly four short sentences, front-loaded with 'Paid.' so the cost signal lands first, then the payload, then payment terms, then the endpoint. Nothing is redundant and nothing needed is buried.

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 parameterless, annotation-free price call with no output schema, the description covers what is returned, what it costs, how to pay, auth requirements, and failure billing. Only the response shape and freshness/refresh semantics are left unspecified, which is a minor gap given the tool's simplicity.

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 the description could add. The embedded endpoint URL usefully confirms that the asset is fixed server-side rather than passed as an argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact asset (Kelp Gain / AGETH) and the exact payload: live USD price, 24h change, market-cap rank. Against a sibling list of hundreds of token-price tools, the token is identified in the first sentence so an agent can tell instantly whether this is the right one.

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 asset name and the data it returns, and the 'Paid. $0.01 USDC' framing tells the agent this is a metered call. However, it never states when to prefer this over the broad price siblings (e.g. buy_crypto_price) or that this endpoint is AGETH-only, so selection is left to inference from the tool name.

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