Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MY

Paid. MetYa (MY) 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/MY.

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

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 it well: it discloses the paid model, the exact price ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits how payment is actually settled and any rate limits, which keeps it 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?

Five short fragments, front-loaded with the payment flag and the asset, then cost, then access requirements. Dense and waste-free, though the telegraphic style trades a little readability for brevity.

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 paid data endpoint with no output schema and no annotations, the description covers the returned fields, the cost and payment chains, auth requirements, failure billing, and the underlying URL. The only real gap is the response format, which is a minor omission for a price lookup.

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 the schema baseline is 4. The description correctly implies a fixed, symbol-specific endpoint with no inputs, and the embedded URL reinforces that nothing needs to be supplied at call time.

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 specific asset (MetYa, symbol MY) and the exact payload: live USD price, 24h change, and market-cap rank. That distinguishes it from unrelated siblings like buy_fx_* or buy_tvl_*, though it never explains how it differs from the near-identical buy_coin_* and buy_crypto_price families.

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. The only selection signal is the leading 'Paid.' and the $0.05 price, which tells an agent this costs money but not why it should be preferred over buy_crypto_price or a buy_coin_MY-style sibling.

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