Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TNSR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses the exact charge, payment currency and network, lack of account or API-key requirements, failure-billing policy, and data sources with a Kraken cross-check. It does not explicitly state that the operation is read-only and executes no trade, nor explain how payment is handled.

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 the paid nature and purpose, followed by cost, authentication, failure billing, and endpoint details. Each fragment adds useful selection or invocation 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 simple fixed-endpoint lookup, it covers the returned metrics, sources, cost, authentication requirements, and failed-call behavior. Because there is no output schema, the absence of response-format details and clearer payment-flow guidance leaves minor completeness gaps.

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 baseline is 4. The fixed TNSR/USD pair and asset-specific URL make the zero-argument invocation unambiguous.

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 TNSR/USD market-data lookup and enumerates the price, range, change, and volume metrics supplied. It clarifies the misleading "buy_coin" name, but does not explicitly distinguish this fixed-asset tool from buy_crypto_price or other siblings.

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?

Usage is implied: choose it when live TNSR/USD statistics from the named exchanges are needed. There is no explicit when-to-use guidance, exclusion, or alternative for other assets or different market-data needs.

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