Skip to main content
Glama

SouthPow crypto & market data

buy_coin_L3

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description itself provides substantial operational detail: a $0.25 USDC charge on Base, no account or API key requirement, no charge for failed calls, and Coinbase Exchange data with a Kraken cross-check. It does not explicitly state that the operation is read-only and executes no coin purchase, leaving some ambiguity created by the tool name.

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?

The description is compact and front-loads the paid nature and live-data scope, then covers cost, access requirements, failure billing, and the URL. Nearly every fragment provides actionable information without filler.

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 market-data call without an output schema, listing the metrics, sources, cost, authentication needs, and failure behavior covers most invocation needs. It could still explicitly distinguish data retrieval from purchasing L3 and clarify the response format or how source discrepancies are handled.

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?

There are no input parameters, so there is no schema-documentation gap to compensate for. The description appropriately establishes the fixed L3/USD scope and supplies the endpoint URL for additional invocation context.

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 identifies a specific resource and dataset: live L3/USD last price, 24-hour open/high/low, percentage change, and 24-hour and 30-day volume. This clarifies the potentially misleading buy_coin_L3 name, but it lacks an explicit retrieval verb and does not differentiate itself from buy_crypto_price or other asset-specific siblings.

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 live L3/USD scope and metric list imply when the tool is useful, while the fee supplies relevant cost context. There is no explicit when-to-use or when-not guidance, nor routing to buy_crypto_price for other assets or different price-data needs.

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