Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VSN

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

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

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 carries the full behavioral burden and does well: it discloses that the call is paid ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — precisely the facts an agent needs before spending money. It does not describe the response shape, latency, or what counts as a 'failed' call, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payload is front-loaded in the first sentence and the operational facts are packed into short clauses with no filler. The raw endpoint URL is a slightly odd fit for an agent-facing description, but it is short and potentially useful for verification.

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 lookup with no output schema, the description covers what it returns, what it costs, which chains to pay on, and the failure-charging policy — enough for an agent to decide and invoke. Response format and how payment is actually transmitted are the only meaningful gaps.

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 description to clarify beyond the schema; per the baseline rule this lands at 4. The description correctly implies no inputs are needed to fetch the quote.

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 a specific resource (Vision / VSN), states the exact payload (live USD price, 24h change, market-cap rank), and the token tag in the name disambiguates it from the hundreds of sibling buy_tok_* entries. It never explicitly contrasts itself with the broader alternatives like buy_crypto_price or the buy_coin_* family, so it stops just short of a 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 context is implied by the payload description (fetch a live quote for VSN) and the payment terms make the cost model explicit, but there is no statement of when to choose this over buy_crypto_price or a buy_coin_/buy_tok_ sibling, nor any exclusion such as 'do not use for historical prices'.

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