Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MTBILL

Paid. Midas mTBILL (MTBILL) 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/MTBILL.

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

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, the description carries the full burden and does well: it discloses cost, accepted payment chains, absence of auth, and the failure-billing policy, plus a concrete endpoint URL. It stops short of describing response format, caching/latency, or freshness guarantees beyond the word 'live'.

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?

Roughly three short sentences, front-loaded with 'Paid.' and the data delivered, followed by cost and access terms. The telegraphic style ('$0.01 USDC on Base or Solana') is efficient, though the bare URL at the end is of marginal use to an agent.

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?

No input schema and no output schema, so the description must supply both purpose and commercial terms — which it does, including the fields returned. Remaining gap is the exact response shape and error behavior, which would matter for a paid call but is only partially implied.

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; the asset is hard-coded in the endpoint. Baseline 4 applies for a parameterless definition.

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 asset (Midas mTBILL / MTBILL) and the exact payload: live USD price, 24h change, and market-cap rank. The token symbol in the tool name plus the description make it distinguishable from the hundreds of sibling buy_tok_* variants, though it never explicitly says 'this is the MTBILL variant, not 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?

It conveys the commercial context ($0.01 USDC on Base or Solana, no account, no API key, no charge on failure), which tells an agent the prerequisites for calling. It gives no guidance on when to pick this over buy_crypto_price or the other token endpoints, so the choice is left to inference from the asset symbol.

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