Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AGI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 load and does well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), the absence of auth requirements, and the billing guarantee that failed calls are not charged. It stops short of stating freshness/latency or error semantics beyond the no-charge rule.

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 price, then the token definition, then the cost/access constraints, then the URL — dense and largely waste-free, though the sentence fragments and trailing bare URL are slightly telegraphic.

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 paid endpoint with no output schema, the description supplies what matters: the returned fields, the cost, the payment chains, and the no-charge-on-failure policy. Freshness of the 'live' price and rate-limit behavior are the only notable omissions.

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?

Zero parameters, so the baseline of 4 applies; nothing to document and nothing misstated.

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?

Names the specific resource (Delysium / AGI token) and the exact payload (live USD price, 24h change, market-cap rank), so an agent can tell it apart from the hundreds of sibling buy_tok_* single-token price tools and from buy_crypto_price.

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 'Paid.' opener plus the $0.01 USDC price and 'no account, no API key' line imply this is the paid single-token price endpoint, but there is no explicit when-to-use/when-not statement or pointer to an alternative (e.g. a free or bulk price tool) if the agent wants to avoid paying.

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