Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GLDY

Paid. Streamex GLDY (GLDY) 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/GLDY.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 behavioral burden and does well: it discloses the paywall, exact price and accepted chains, absence of authentication, and the failure-billing policy, all of which an agent needs before committing a paid call. Rate limits and latency are not covered.

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?

The text is dense and front-loaded: paywall flag first, then payload, then payment/auth terms, then endpoint. The telegraphic phrasing ('URL https://...') is slightly clipped but wastes no words.

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?

There is no output schema, so the description must describe return values, and it does list the three returned fields. With payment mechanics, auth and failure policy all present, the only missing element is response shape or format detail.

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 baseline is 4; the description adds nothing to mis-describe an empty schema and correctly indicates the asset is fixed by the tool itself rather than passed in.

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 asset (Streamex GLDY) and enumerates the returned data: live USD price, 24h change and market-cap rank. The 'Paid.' prefix signals the paid tier that separates this family from the free buy_coin_* siblings, though it does not explicitly contrast with any specific sibling.

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?

Prerequisites are spelled out ($0.01 USDC on Base or Solana, no account or API key, failed calls not charged), which effectively tells an agent when the call is viable. However, there is no explicit statement of when to prefer this over a free alternative or when-not-to-use it.

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