Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MCAT

Paid. Marscat Token (MCAT) 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/MCAT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 behavioral burden and does well: it discloses the paid nature, exact price and accepted payment chains, that no authentication is required, that failed calls are not charged, and the underlying endpoint. What it omits is data freshness/latency and rate-limit behavior, which matter for a live price feed.

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 single most decision-relevant fact ("Paid."), then the payload, then cost/auth/failure terms, then the raw URL. The telegraphic fragment style is efficient, though the bare "URL https://..." fragment reads as appended metadata rather than prose.

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-annotation, no-output-schema endpoint, the description covers nearly everything an agent needs before spending money: what it returns, what it costs, how to pay, and that failures are free. Only freshness/staleness and response shape details 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. It correctly avoids inventing parameter talk and instead spends its words on cost and return content.

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?

Names the specific resource (Marscat Token / MCAT) and the exact payload (live USD price, 24h change, market-cap rank), so an agent can tell instantly that this is the MCAT-specific price feed rather than one of the hundreds of sibling buy_tok_* or buy_coin_* endpoints.

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 implied rather than stated: the description establishes the payment precondition ($0.05 USDC on Base or Solana) and that no account or API key is needed, which tells an agent it *can* call this. However, it never says when to prefer this over alternatives (e.g. buy_crypto_price or buy_tok_* lookups) or what to do if a call fails.

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