Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MEY

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It discloses that access is paid, the cost and chains, that no account or API key is needed, and that failed calls are not charged. It does not cover rate limits or payment mechanics.

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?

The text is compact and front-loaded: 'Paid' first, then the resource and returned fields, followed by cost, access requirements, and failure billing. Every sentence carries useful information without waste.

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-parameter price lookup, the description covers the token, returned fields, cost, access, and failure billing. It does not spell out the payment handoff or response format, but those gaps are minor given the tool's simplicity and the absence of an output schema.

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 and the empty input schema is fully documented. The description adds no parameter semantics, but none are needed for this call. The baseline score of 4 applies.

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 token (Mey Network/MEY) and enumerates the exact data returned: live USD price, 24h change, and market-cap rank. It is clear what the tool provides, but it does not use an explicit verb or distinguish this from the sibling buy_coin_ME endpoint.

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?

It states cost and access requirements (paid; $0.01 USDC on Base or Solana; no account/API key), but gives no explicit when-to-use or when-not-to-use guidance. It also never mentions the sibling buy_coin_ME or other price alternatives, so usage is only implied by the token name.

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