Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LINGO

Paid. Lingo (LINGO) 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/LINGO.

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

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 carries the burden and does substantial work: it declares the tool is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. Missing are any statement about rate limits, price freshness/latency, or what an on-chain payment failure looks like.

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?

Roughly four short sentences with the paid/cost fact front-loaded and the endpoint URL last. The telegraphic fragment style ('Paid.') is efficient rather than wasteful, though the trailing raw URL is of limited value to an agent that cannot call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema price lookup, the description covers what is returned, what it costs, which chains payment settles on, that no credentials are needed, and the failure-billing policy. That is the full set of facts an agent needs to decide and invoke correctly.

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 input schema is an empty object with no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the symbol is pinned in the tool itself rather than passed in.

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 specific resource (Lingo / LINGO) and the exact payload: live USD price, 24h change, market-cap rank. That is enough to distinguish it from the hundreds of sibling buy_tok_* tools at a glance. It stops short of contrasting it with adjacent options such as buy_crypto_price.

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 by the content — an agent needing a LINGO spot quote would pick this — but there is no explicit when-to-use statement, no exclusion, and no pointer to an alternative like buy_crypto_price or buy_coin_LINGO. The agent must infer selection from the symbol in the name alone.

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