Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MARSCOIN

Paid. MarsCoin (MARSCOIN) 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/MARSCOIN.

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

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 supplied, the description carries the full burden and does well: it discloses that the call costs $0.01 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged. That is exactly the behavioral context an agent needs before invoking a paid tool. It stops short of describing response latency, timeout handling, or the shape of the returned payload.

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?

Five short, front-loaded fragments: purpose, payload fields, price, payment rails, and the endpoint URL. Nothing is repeated and every clause earns its place.

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-parameter, no-output-schema paid endpoint, the description covers what matters: what it returns, what it costs, how to pay, and that failures are free. The absence of an output schema is offset by the enumerated return fields. Only the exact response shape and error semantics are left implicit.

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 input schema has zero parameters, so there is no parameter meaning to add and the baseline applies. The description correctly implies the call takes no arguments by hard-coding the symbol and endpoint.

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?

States a specific verb and resource: it returns the live USD price, 24h change, and market-cap rank for MARSCOIN. That is far more informative than the bare name. It does not, however, explain how it differs from near-identical siblings such as the buy_coin_* token family or buy_crypto_price, so an agent must infer the distinction from the symbol in the name.

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 only implied: the description makes clear this is the price endpoint for MARSCOIN specifically. There is no explicit statement of when to choose this over buy_crypto_price or the buy_coin_* variants, and no exclusion or prerequisite guidance beyond payment cost.

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