Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MARSMI

Paid. MarsMi (MARSMI) 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/MARSMI.

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

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 supplied, the description carries the full behavioral burden and does well: it discloses that the call is paid at $0.01 USDC, that payment settles on either Base or Solana, that no auth or API key is required, and that failed calls are not charged. The remaining gap is that it does not state latency, caching, or freshness guarantees for a 'live' price.

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?

It is front-loaded with the payoff (what data you get) and then the commercial terms, in five compact clauses with no filler. The telegraphic 'Paid.' opener and raw URL are slightly abrupt but each element is actionable, and nothing can be removed without losing information.

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, single-token price lookup with no output schema and no annotations, the description covers the return contents, the payment model, the supported chains, and the auth posture. That is essentially everything an agent needs to decide and call correctly; only the exact response shape and freshness semantics remain unspecified, and those are minor here.

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 there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies the token and quote currency are fixed by the tool itself rather than passed in, which prevents an agent from hunting for a symbol argument.

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 resource (MarsMi / MARSMI) and enumerates the payload: live USD price, 24h change, and market-cap rank. That lets an agent tell it apart from the hundreds of sibling buy_tok_* entries by token symbol alone, though it never explicitly states how it differs from buy_crypto_price or buy_coin_MARSCOIN, which cover adjacent ground.

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?

It supplies practical invocation context (cost, accepted chains, no account or API key needed, no charge on failure), which is genuinely useful before calling. However, it gives no explicit when-to-use or when-not-to-use guidance relative to the sibling price tools, so the agent must infer that this is the MARSMI-specific alternative to the generic price endpoint.

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