Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FUN

Paid. FUNToken (FUN) 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/FUN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 burden and does well: it discloses that the call is paid, the exact cost and payment chains ($0.05 USDC on Base or Solana), that no credentials are needed, that failed calls are not charged, and the endpoint. It omits rate limits and error/response framing, but the cost and failure policy are exactly the traits an agent needs before spending money.

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 critical 'Paid.' marker, then purpose, then cost and payment rails, then access constraints, then the URL — no sentence is filler. The telegraphic style suits a machine-read 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?

No output schema exists, so the description correctly names the returned fields and adds payment, credential, and failure-charge policy for a paid financial endpoint. It is missing only response-shape details (e.g., units, timestamp/freshness) that would let the agent reason about the data quality after the call.

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 no parameter semantics to explain and the payoff baseline of 4 applies. The description instead spends its words on the returned fields and payment mechanics, which is the right use of space.

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?

Names a specific resource (FUNToken/FUN) and enumerates the returned data (live USD price, 24h change, market-cap rank), so the agent knows exactly what it buys. It does not, however, distinguish itself from near-neighbors like buy_coin_FUN1 or buy_crypto_price, so the agent still has to guess which price tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the many sibling price tools (buy_coin_FUN1, buy_crypto_price). Only incidental prerequisites ('no account, no API key') hint at the context, leaving alternative selection entirely to inference.

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