Skip to main content
Glama

SouthPow crypto & market data

buy_econ_mx

Paid. Economic data for country MX: GDP, GDP growth, inflation, unemployment, population, GDP per capita (latest World Bank values). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/economic/mx.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 behavioral burden and does much of it well: it discloses that the call costs $0.01 USDC, the accepted chains, that no account or API key is needed, and that failed calls are not charged – all material facts a caller needs before spending funds. It stops short of describing the response shape, data freshness beyond 'latest', or any rate limits, which keeps it out of the top band.

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?

Four terse sentences, front-loaded with the two facts that gate the call ('Paid.' and the price), then the data scope, then the operational details. Every clause earns its place and nothing is padded.

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?

Given a zero-parameter, no-annotation, no-output-schema tool, the definition covers identity, data source, payment mechanics, and call preconditions, which is most of what an agent needs to invoke it safely. The remaining gap is the return format and units/currency of the economic figures, which matters for a data-returning tool with no output schema.

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 baseline of 4 applies. The description does not waste space restating a non-existent schema and instead uses that space for payment and source context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: economic data for country MX, with the exact indicators enumerated (GDP, GDP growth, inflation, unemployment, population, GDP per capita) and the data source (latest World Bank values). This clearly distinguishes it from the many sibling country tools like buy_econ_us or buy_econ_br, which an agent can route to without opening any schema.

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 by the country-specific framing – an agent should pick this when it needs Mexican macro data. It also clarifies payment preconditions ('Paid', '$0.01 USDC on Base or Solana', 'No account, no API key'), which helps an agent decide whether it can call at all. However, there is no explicit when-to-use/when-not guidance or pointer to alternative tools for other countries or other indicator sets.

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