Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MTX

Paid. Matrix (MTX) 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/MTX.

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

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 full burden and does substantial work: it declares the tool is paid, quotes the exact price, names the two accepted settlement chains, confirms no account or API key is required, and guarantees failed calls are not charged. That last point is a meaningful risk disclosure for a metered endpoint. It stops short of describing response shape or latency, which keeps it from a 5.

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 fragments, front-loaded with "Paid." so the cost signal lands first, followed by what is returned, then the price/chain terms, then the endpoint URL. Nothing is redundant and nothing an agent needs is buried.

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, output-schema-less purchase endpoint, the description covers what is returned, the cost, the payment rails, and the failure-charge policy. The remaining gap is response format detail, but with no output schema and trivial input surface, this is close to complete.

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 nothing for the description to disambiguate and the baseline is 4. The description correctly adds no parameter noise.

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?

"Matrix (MTX) price: live USD price, 24h change and market-cap rank" names the resource and enumerates the exact fields returned, so the agent knows precisely what it gets. The ticker in the name and the parenthetical disambiguate it from the many other buy_tok_* siblings, though it never explicitly contrasts itself with the generic buy_crypto_price.

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 rather than stated: an agent infers it should call this when it needs the MTX spot price. Payment mechanics ($0.01 USDC on Base or Solana, no account or API key) tell the agent the preconditions for calling, which is real context. However, there is no explicit when-not guidance and no named alternative such as buy_crypto_price.

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