Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MGLO

Paid. Midas Fasanara Global Open (MGLO) 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/MGLO.

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

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 the cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. 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?

Front-loaded with 'Paid.' followed by purpose, cost, access terms, and endpoint URL in a compact telegraphic style. Every sentence carries information, though the fragment style is slightly terse and the URL could be considered optional noise.

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, rank), the payment model, and access requirements, which is nearly everything an agent needs. Only rate limits and error/response shape are unaddressed.

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 the baseline is 4; there is nothing for the description to disambiguate. The URL is included, which is mildly useful but not a parameter concern.

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 Fasanara Global Open / MGLO) and states exactly what is returned: live USD price, 24h change, and market-cap rank. It is clearly distinguishable from the mass of buy_tok_* siblings by the token name, though it never explicitly says 'use this only for MGLO' or points to a general alternative like 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 implies usage (fetch MGLO price data) and gives practical context (paid, no account, no API key), but offers no explicit when-to-use/when-not guidance or comparison to sibling tools such as buy_crypto_price or buy_coin_* that might also return price data. The agent must infer selection from the token name alone.

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