Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NEET

Paid. Not in Employment, Education, or Training (NEET) 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/NEET.

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

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, the description carries the full burden and does well: it discloses that the call is paid, the exact cost and payment chains, that no credentials are needed, and that failed calls are not billed. It omits rate limits, latency, and whether the quoted price is a snapshot or streaming, which keeps it from 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?

Front-loaded with "Paid." and then a compact, comma-separated block of facts — payment, access, billing guarantee, URL — with no filler. The parenthetical expansion of NEET is slightly bulky but earns its place as ticker disambiguation.

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 price endpoint, the description covers what is returned, what it costs, how to pay, and where it lives, which is close to everything an agent needs before invoking. Only the response shape details and any freshness guarantee are left implicit.

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 schema has zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the single fixed resource rather than inventing parameter semantics.

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 concrete resource (NEET token price) and the exact payload: live USD price, 24h change, market-cap rank. It even spells out the NEET acronym, which disambiguates the ticker. It does not differentiate from the mass of sibling endpoints (buy_coin_*, buy_crypto_price, buy_tok_*), so it stops short of a 5.

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?

Gives purchasing context — price of $0.05 USDC, payable on Base or Solana, no account or API key, failed calls not charged — which tells an agent the preconditions for calling. However, it never says when to pick this tool over the near-identical siblings or what the alternative is for a different token or a broader price feed.

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