Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MED

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 burden and does unusually well: it discloses that the call is paid, the exact cost ($0.01 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits and the response shape, so it falls short of 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?

Every clause carries information — payload, price, rails, auth posture, failure billing, endpoint — with no filler, and the 'Paid.' lead is front-loaded. The telegraphic, fragment-heavy style costs it a little readability.

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, no-output-schema price lookup, the description covers what is returned, what it costs, how to pay, and what happens on failure — enough for an agent to decide and call correctly. Minor gaps are the absence of rate limits and any indication of latency or caching freshness for the 'live' price.

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 no parameter semantics to explain; the baseline for a 0-param tool is 4. The description implicitly confirms this by embedding the asset (MED) in the endpoint itself rather than accepting it as an argument.

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 concrete resource (Medibloc / MED) and enumerates the payload: live USD price, 24h change, and market-cap rank. That is far more than a restatement of the tool name. It does not differentiate from the generic sibling buy_crypto_price or explain why a per-asset endpoint exists, which keeps it off 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite an obvious generic competitor (buy_crypto_price) and hundreds of sibling buy_tok_* endpoints. The payment and access notes are practical context but not selection guidance.

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