Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SSV

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

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

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 full burden and handles the important parts: it is a paid call, the price is $0.01 USDC on Base or Solana, no account or API key is required, and failed calls are not charged. It omits how payment is actually settled and any rate limits, which leaves a gap for an agent that must arrange funds before invoking.

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?

Six short fragments, no filler, and the payload description is front-loaded before cost, payment rails and billing policy. The raw endpoint URL at the end is useful rather than padding for a paid HTTP service.

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 read with no output schema and no annotations, the description covers what is returned, what it costs, on which chains, and the failure-billing policy. The main missing piece is the mechanics of paying the $0.01 USDC, which an agent needs before calling but may be handled at the transport layer.

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 and the description does not invent any, so there is no semantic gap to fill. Baseline for a 0-parameter schema applies, with the endpoint URL providing the only caller-side detail 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?

The description names the exact resource (SSV Network price) and enumerates the returned fields: live USD price, 24h change and market-cap rank. That is far more specific than a generic price tool, but it never distinguishes itself from generic siblings like buy_crypto_price or the buy_coin_* family, so an agent must infer selection from the ticker in the tool 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 only implied by the content ('price'), with no explicit statement of when to prefer this over buy_crypto_price or other SSV-adjacent tools, and no exclusions. What guidance exists is commercial rather than selection-oriented: pay $0.01 USDC on Base or Solana, no account or API key needed.

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