Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CARV

Paid. CARV (CARV) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CARV.

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

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 ($0.01), which chains/payment assets are accepted, that no account or API key is needed, and critically that failed calls are not charged. It leaves out rate limits or data freshness guarantees beyond the word 'live'.

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.' then the payload description, cost, terms, and endpoint URL in a few dense sentences with little waste. Minor redundancy in 'CARV (CARV)' is the only slack.

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 parameterless price endpoint with no output schema and no annotations, the description covers what is returned, the cost, the payment mechanics, and the failure policy—enough for an agent to decide and call correctly. Freshness cadence is the only notable omission.

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 to disambiguate; the baseline is 4. The description reinforces this by noting no account or API key is required, confirming the call is argument-free.

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 specific resource (CARV token) and enumerates exactly what is returned: live USD price, 24h change, market-cap rank. The token symbol in name and description distinguishes it from the hundreds of sibling buy_tok_* tools. It does not explain how it differs from the broader buy_crypto_price, keeping it from 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?

The payment context ('$0.01 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged') frames the cost of calling, and the token name implies when it is relevant. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives like buy_crypto_price for general price lookups.

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