Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MVL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose the monetization profile well (paid, $0.01 USDC on Base or Solana, no account/API key, failed calls not charged, direct URL), but the payment mechanism is never explained and no response shape, latency, or caching behavior is described. For a paid call this is partial disclosure.

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?

A tight, front-loaded sequence: payment flag first, then the data returned, then cost/rails, then access conditions and URL. No redundant wording; every clause carries information an agent needs before paying.

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 parameterless, paywalled quote tool with no output schema, the description covers price, cost, payment rails, refund policy and endpoint, which is most of what is needed. The remaining gap is how payment is actually made and what the response looks like, which is material for a paid call.

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 schema has zero parameters, so there is nothing for the description to disambiguate. The description correctly gives no parameter guidance, and the quoted payload fields help interpret the result.

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 payload: 'MVL (MVL) price: live USD price, 24h change and market-cap rank', and the 'buy_tok_MVL' name pins the token, so an agent knows exactly which asset's quote it gets. It does not, however, contrast itself with the generic sibling buy_crypto_price, so the differentiation is by token rather than by stated scope.

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 — the agent must infer that this is the tool for MVL quotes. The cost, chain and no-account conditions are stated, but there is no explicit 'use this instead of buy_crypto_price when…' routing and no statement of when-not to call it.

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