Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AIC

Paid. AI Companions (AIC) 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/AIC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full behavioral burden and does well: it discloses the $0.05 USDC cost, accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — key facts for a paid endpoint. It stops short of describing latency, rate limits, or response format, but the core commercial behavior is transparent.

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 the resource and payload ('Paid. AI Companions (AIC) price: live USD price, 24h change and market-cap rank'), followed by cost, chain, and terms in short clauses. Nearly every sentence earns its place, though the raw URL at the end is somewhat redundant for an agent that invokes the tool rather than fetching it.

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, single-value lookup with no output schema, the description covers what is returned, what it costs, how payment works, and that failures are free. That is close to sufficient for correct invocation; only rate limits or freshness guarantees are 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 there is nothing for the description to disambiguate; the baseline applies. The description does not waste space restating a schema that does not exist.

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 (AI Companions / AIC) and exactly what is returned: live USD price, 24h change, and market-cap rank. It is clearly distinguishable from the hundreds of sibling buy_tok_* tools by naming the token, though it does not explicitly point to buy_crypto_price or buy_coin_* for other lookup patterns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Paid.' and lists the cost and chains, which implies a transactional context, but it never states when to use this tool versus alternatives (e.g., buy_crypto_price for arbitrary tokens) or any preconditions beyond payment. There are no exclusions or routing guidance, so an agent must infer the decision from the tool name alone.

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