Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VBILL

Paid. VanEck Treasury Fund (VBILL) 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/VBILL.

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

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 load well: it discloses cost ($0.05 USDC on Base or Solana), no-account/no-key access, and that failed calls are not charged. That is meaningful behavioral context beyond a structured field. It doesn't describe the response payload shape or latency/rate behavior.

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?

Extremely tight — the key facts (asset, returned fields, price, payment chains, no auth, failure policy, URL) are packed into a few front-loaded fragments with zero filler.

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 simple zero-param paid price lookup with no output schema, the description covers what the agent needs: what data comes back, how to pay, and where the endpoint is. Slightly incomplete on response format and payment-flow mechanics, but strong overall.

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 0 parameters, so the baseline of 4 applies. The description correctly signals no inputs are needed and embeds the asset identifier and endpoint URL directly.

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?

Names the specific resource (VanEck Treasury Fund, VBILL) and the data returned: live USD price, 24h change, market-cap rank. It is clearly a price-lookup tool. It doesn't explicitly differentiate from the dense buy_tok_* sibling set beyond the ticker, which is already in the name.

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 implied (fetch VBILL price) but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as buy_yields_protocol_vaneck-treasury-fund for yield data. Implied usage only.

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