Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MBG

Paid. MBG By Multibank Group (MBG) 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/MBG.

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

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 that the call is paid ($0.05 USDC), the accepted rails (Base or Solana), that no account or API key is required, and that failed calls are not charged. That failure-billing policy is exactly the kind of non-obvious behavior an agent needs before spending money. It omits rate limits and response format details, keeping it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short, front-loaded with the 'Paid' flag and the purpose, then pricing, then access terms. Every clause carries information; the trailing raw URL is the only borderline element, and even that is arguably useful for direct invocation.

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 tool, the description covers what is returned (price, 24h change, market-cap rank), the cost, the payment chains, and the auth-free access — enough for an agent to call it correctly. Missing only secondary detail such as response encoding or rate limits.

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 and the description correctly says nothing about inputs, which is the right call. Baseline for a parameterless tool is 4, and there is no misleading input talk.

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 a specific resource ('MBG By Multibank Group (MBG) price') and enumerates the exact payload (live USD price, 24h change, market-cap rank), so an agent can tell this apart from the other buy_tok_* siblings by ticker. It does not explicitly contrast with the generic buy_crypto_price or buy_coin_MBG-style siblings, so sibling differentiation is implied rather than stated.

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 context is implied by the token name and the listed outputs, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative (e.g. a generic price tool or a category index) to route against. The payment and access notes tell the agent how to call it, not why to pick it over a sibling.

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