Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GRASS

Paid. GRASS/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/GRASS.

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

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 behavioral burden and does well: it discloses that the call is paid ($0.002 USDC on Base), that no auth is needed, and that failed calls are not charged — all non-obvious traits. It omits remaining behavioral facts such as whether payment is per-call or session-based, expected latency, and rate limits, which keeps it out of the top score.

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?

The single dense sentence is front-loaded with the most important qualifier ('Paid.') and then the payload, with pricing and access terms trailing. Nothing is padded, though the raw endpoint URL adds little for an agent that cannot choose a different URL.

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?

There is no output schema, so the field enumeration (last, open/high/low, % change, 24h/30d volume) does the job of describing returns. Combined with the cost and access disclosures, an agent has what it needs to decide and invoke; only freshness/update cadence and failure modes are left unstated.

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 is 4 and there is nothing for the description to clarify. It does not add noise about parameters, which is correct.

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 the exact resource (GRASS/USD) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume, with named data sources (Coinbase Exchange, Kraken cross-check). That is specific and unambiguous. It stops short of 5 because it never refers to siblings — with 250+ buy_coin_* tools, an explicit 'use the matching buy_coin_<SYMBOL> tool for other tokens' would have fully closed the loop.

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?

The description implies usage (live price data, paywalled) and supplies decision-relevant facts: cost, chain, no account or API key required, failed calls not charged. However, it gives no explicit when-to-use vs when-not, and it does not route the agent to alternatives such as the generic buy_crypto_price tool or explain when the 30d volume field matters.

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