Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANVL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a respectable job: it discloses the paid nature, exact price and payment chains, absence of auth requirements, the refund policy on failures, and the underlying endpoint URL. It omits freshness/latency, rate limits, and whether the call is a simple GET, which keeps it out of the top band.

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 with 'Paid.' then purpose, then cost/payment rails, then guarantees and URL — a sensible order for an agent deciding whether to spend. Sentences are telegraphic but every one carries distinct information; only the trailing raw URL is arguably redundant since it is derivable from the name.

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

Completeness3/5

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

For a zero-param, no-output-schema tool this covers cost, payment, auth, failure policy, and the three returned data fields, which is most of what an agent needs. It still leaves the response shape (field names, units, timestamp) and data freshness undefined, which matters for a live-price product.

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 for the schema to document and the baseline of 4 applies. The description correctly implies the call is fully determined by the endpoint (ticker baked into the URL), so no parameter guidance 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 and verb: 'Anvil (ANVL) price' with the exact payload — live USD price, 24h change, market-cap rank. That is far more informative than a bare ticker tool name. It stops short of differentiating itself from the large family of buy_coin_* / buy_token-style price siblings, so an agent still cannot tell why to pick this one over those.

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?

Implied usage is clear (get ANVL's current price), and the description does give real usage context: it is a paid call at $0.05 USDC on Base or Solana, with no account or API key required, and failed calls are not charged. However, it never says when to prefer this over a sibling price tool, nor any exclusion or budget consideration for the many other paid ticker 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