Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MBL

Paid. MovieBloc (MBL) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/MBL.

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

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 burden and does well: it declares the tool is paid, names the exact price and the two accepted payment chains, confirms no authentication is required, and specifies that failed calls are not charged — a genuinely useful retry policy. What it omits is response behavior beyond the field list, such as latency, rate limits, or error shapes.

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?

Three tight sentences, front-loaded with the payment flag and the returned fields before the practical details. The raw endpoint URL is arguably redundant with the tool name but still useful for verification; nothing else is 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 zero-parameter, no-output-schema paid endpoint, the description covers the essential unknowns: what data is returned, what it costs, how to pay, and that failures are free. It stops short of describing the response payload shape or error behavior, which matters slightly more here because no output schema exists to fill the gap.

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; baseline 4 applies. The description correctly implies the symbol is baked into the endpoint (the URL path ends in /MBL), which reinforces that no arguments are needed.

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 resource and verb-equivalent: MovieBloc (MBL) USD price with 24h change and market-cap rank. The agent knows exactly what data comes back. However, it gives no hint of how this differs from the many sibling families that also return token prices (buy_coin_*, buy_crypto_price, buy_tok_* variants), so differentiation is left to the name alone.

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?

Provides operational context — $0.05 USDC on Base or Solana, no account or API key, failed calls not charged — which tells the agent what it costs and that it is callable unconditionally. It never states when to choose this over a sibling price tool (e.g., buy_coin_MBL-adjacent or buy_crypto_price), nor any exclusions, so the selection decision is only implied by the token 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