Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VIN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 real work: it discloses that the call is paid, costs $0.05 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged — the key risk facts for an agent. It stops short of describing response format, latency, or rate limits.

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 the decisive fact ('Paid.') followed by the resource and payload, then cost and access terms. Nearly every clause earns its place; the trailing raw URL is slightly redundant with the tool's purpose but still practical.

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-param, no-output-schema, no-annotation tool, this is close to sufficient: it names the returned fields, the price, the payment mechanics, and the auth posture. The main gap is any indication of response shape or freshness beyond 'live', but nothing blocks correct invocation.

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 has zero parameters, so the schema baseline applies and there is nothing to disambiguate. The description usefully specifies the payment asset and chains (USDC on Base or Solana), which acts as implicit caller-side context even though no input fields exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (VulgarTycoon / VIN price) and the exact payload: live USD price, 24h change, market-cap rank. Despite ~1000 sibling buy_tok_*/buy_coin_* tools, an agent can tell this fetches VIN price data without opening anything else.

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 by the resource name rather than stated: an agent infers 'call this when you need VIN's price.' It never names alternatives (e.g. buy_crypto_price, buy_coin_* series) or says when not to use it, which matters given the enormous sibling set.

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