Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GLM

Paid. GLM/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/GLM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description discloses unusually useful operational behavior: calls are paid, cost exactly $0.01 USDC on Base, require no account or API key, and are not charged when they fail. Naming Coinbase Exchange and the Kraken cross-check also clarifies data provenance.

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 description is compact and front-loads its paid nature and data scope, followed by cost, access, failure-billing, and endpoint details. Every fragment contributes actionable information without filler.

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-argument market-data tool, it covers the returned metrics, sources, price, payment rail, authentication requirements, failure behavior, and URL, making correct invocation straightforward. With no output schema, the exact response structure remains unstated, and the potentially misleading buy_coin naming is not explicitly resolved.

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?

There are no parameters, so the zero-input baseline applies and there are no undocumented arguments requiring compensation. The fixed GLM endpoint further confirms that asset selection is built into the tool rather than supplied at invocation.

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 clearly identifies a live GLM/USD market-data resource and enumerates its exact metrics, distinguishing it from siblings for other assets. However, it lacks an explicit retrieval verb and does not directly clarify that, despite the buy_coin name, it provides price data rather than purchasing GLM.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The fixed pair, live scope, and listed 24-hour and 30-day metrics provide clear context for choosing it when current GLM market data is needed. It does not explicitly explain when to prefer it over buy_crypto_price or another alternative.

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