Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SKYAI

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

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

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 supplied, the description carries the full disclosure burden and does a good job: it flags the call as paid, states the exact price and accepted chains, confirms no authentication is needed, and notes that failed calls are not charged — a genuinely useful billing behavior. It omits rate limits, latency/data freshness, and what a success payload 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 dense and front-loaded: 'Paid.' leads, then the data payload, then payment terms, then the endpoint. Almost every clause carries signal; the raw endpoint URL is the one element that borders on filler for an agent that never constructs the request itself.

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, no-output-schema purchase tool, the description covers the essentials an agent needs to decide and act: what data comes back, what it costs, how to pay, and that failures are free. Only secondary details like rate limits or response shape are absent, and those are lower stakes 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, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly adds no parameter chatter.

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 asset (SkyAI/SKYAI) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is far more specific than the bare tool name, though it never explicitly distinguishes itself from the generic sibling buy_crypto_price or from buy_tok_XAI, leaving the agent to infer the per-token split.

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 gives real usage context — paid, $0.01 USDC on Base or Solana, no account or API key required, failed calls not charged — which tells the agent the prerequisites for calling. However, it offers no when-to-use/when-not guidance relative to the hundreds of sibling buy_tok_* tools or buy_crypto_price, so selection still relies on the token symbol in the 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