Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CYS

Paid. Cysic (CYS) 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/CYS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 unusually well: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits and response shape, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the single most important fact ('Paid') and then packs purpose, price, payment rails, auth status, billing policy and endpoint into one tight block with no filler. Everything present affects the decision to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 lookup, this is complete: the agent knows what it returns, what it costs, how to pay, that no credentials are needed, and that failures are free. Nothing required to invoke it correctly is 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; baseline 4 applies. The URL it supplies is a reasonable stand-in for identifying the exact endpoint variant.

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?

States a specific verb implied (purchase/fetch) plus an exact resource — Cysic (CYS) USD price — and enumerates the three returned data points (live price, 24h change, market-cap rank). Against hundreds of near-identical buy_tok_* siblings, naming the ticker and payload is exactly the differentiator an agent needs.

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?

Implied usage is clear (call this when you need a CYS quote), and the payment terms tell the agent what it costs before invoking. However, it never names alternatives such as buy_crypto_price or buy_coin_CYS, so an agent cannot tell from the description when a different price tool would be the better pick.

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