Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LINEA

Paid. LINEA/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/LINEA.

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

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 usefully discloses the $0.002 USDC charge, Base network, lack of account or API-key requirements, failed-call charging policy, and exchange sources with Kraken cross-checking. It does not explicitly state that the operation is read-only or explain the payment and response mechanics.

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 exact data offering before cost, access, failure, and endpoint details. Each fragment supplies 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-input, fixed-asset lookup, it covers the metrics, sources, cost, authentication, failure behavior, and invocation URL well. Because there is no output schema, some response-format detail would help, and explicit confirmation that this retrieves data rather than buys LINEA would remove residual ambiguity.

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 has no parameters, so there are no argument semantics requiring documentation. The fixed LINEA endpoint reinforces that asset selection is already baked into the tool and no input is needed.

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 clearly identifies live LINEA/USD market data and enumerates the exact price, range, change, and volume metrics provided. Its fixed LINEA scope distinguishes it from other coin-specific siblings, though it lacks an explicit retrieval verb and does not clarify that no coin purchase occurs despite the tool name.

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 for agents needing current LINEA/USD pricing and volume statistics. There is no explicit when-to-use guidance, exclusion, or direction to the generic buy_crypto_price sibling for other assets or different requirements.

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