Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SOLV

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

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

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 full burden and does substantive work: it declares the tool is paid, names the exact price and accepted rails ($0.05 USDC on Base or Solana), confirms no account or API key is needed, and states failed calls are not charged. It does not describe rate limits, latency, or freshness guarantees, keeping it below a 5.

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?

Four short sentences, each carrying distinct information: payment flag, data payload, cost and payment rails, access constraints and billing policy. Front-loaded with 'Paid.' so the agent sees the cost implication first. Nothing is redundant.

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 paid price endpoint with no output schema, the description covers commercial model, payment method, access requirements, billing on failure, and the fields returned. It is complete enough to call correctly; only return-shape detail (format, timestamp) is left unspecified.

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 of 4 applies. The description correctly implies no inputs are required by noting no account or API key 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?

States a specific resource (Solv Protocol SOLV) and the exact payload: live USD price, 24h change, market-cap rank. An agent can tell this is a single-asset price lookup. It does not distinguish itself from generic price siblings such as buy_crypto_price or buy_coin_SOLV, so it stops short of 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?

Usage is only implied by the asset-specific naming: call it when you want SOLV pricing. There is no explicit when-to-use/when-not guidance and no pointer to the cheaper or broader alternatives (buy_crypto_price, buy_coin_SOLV) that an agent should compare against.

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