Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DOLA

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

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

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 supplied, the description does real work: it discloses that the call is metered ($0.01 USDC), the accepted payment rails (Base or Solana), that no account or API key is required, and the billing policy for failures ('Failed calls not charged'). What it omits is data freshness/latency, rate limits, and error semantics beyond billing, which matters for a paid quote endpoint.

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 and telegraphic: 'Paid.' immediately flags cost, then the payload, then price/rails, then billing policy, then the endpoint URL. Every sentence adds a distinct fact. Minor waste in 'DOLA (DOLA)' and the trailing bare URL, but nothing is padded.

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, no-output-schema tool this covers most of what an agent needs: what comes back (price, 24h change, rank), what it costs, how to pay, and that failures are free. The main gap is the absence of any freshness or reliability statement for a 'live' price feed, and no guidance on parsing the response given there is no output schema.

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 no schema semantics to supplement and the baseline of 4 applies. The description correctly avoids inventing pseudo-parameters and instead spends its words on output fields and payment mechanics.

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 states a specific resource (DOLA) and the exact payload it returns: live USD price, 24h change, and market-cap rank. That is far more informative than a tautology. However, it never distinguishes this tool from near-identical siblings such as buy_coin_DOLA or buy_crypto_price, so an agent cannot tell why it should pick this one without inspecting several definitions.

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 only implied: an agent can infer it should call this when it wants a DOLA spot quote. There is no explicit when-to-use, no when-not-to-use, and no mention of the obvious alternatives (buy_coin_DOLA, buy_tok_* variants, generic buy_crypto_price) in a catalogue with hundreds of overlapping price tools. The payment note ('$0.01 USDC on Base or Solana') hints that this is a paid endpoint but does not help route between tools.

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