Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EDU

Paid. Open Campus (EDU) 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/EDU.

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

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 at all, the description carries the full burden and does well: it discloses the cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. The notable gap is that it never explains how the payment is actually executed by the agent (payment protocol, header, or pre-authorization), which is the main behavioral unknown for a paid endpoint.

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?

It is short, front-loaded with 'Paid.' and the resource, and every clause carries information (cost, chains, auth, failure billing, endpoint). The telegraphic fragment style is efficient but reads as a price-list blurb rather than a structured definition.

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 tool the description is nearly complete: it states the returned metrics, the price, the payment rails, and the auth model. Only the mechanics of paying and the response format remain unstated, which are the last pieces an agent would need before invoking it.

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 of 4 applies; there are no inputs whose meaning could be clarified or obscured. The description correctly implies the token is fixed by the tool itself rather than passed as an argument.

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 a specific resource and scope: 'Open Campus (EDU) price: live USD price, 24h change and market-cap rank', so an agent knows exactly what data comes back. It does not, however, distinguish itself from near-identical siblings such as buy_coin_* price tools or buy_crypto_price, leaving the agent to infer why buy_tok_EDU is the right choice.

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 only implied: it is a paid quote for one specific token, so the agent can infer 'call this when you want the EDU price'. The leading 'Paid.' plus the $0.01 price tag hints that cheaper or free alternatives may exist, but no alternative tool is ever named and there is no when-not-to-use guidance.

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