Skip to main content
Glama

Macro labor

macro_labor
Read-onlyIdempotent

Official World Bank labor market, unemployment, CPI inflation, GDP growth/per-capita for 1-5 countries plus US Treasury interest rates & public debt. Not advice. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "macro_labor"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNo1-5 comma-separated ISO-2/3 country codes (default USA)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds the material behavior an agent actually needs: cost of $0.003 per call, accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the two-step auth handshake, and a 'not advice' disclaimer. It does not mention rate limits, data freshness, or what a failed payment returns.

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?

Four tight sentences, front-loaded with what data is returned before moving to price and the payment handshake. The 'Not advice' clause is a short, purposeful disclaimer rather than filler. No wasted phrasing, though the payment mechanics could be compressed slightly.

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 two-parameter, read-only data-fetch tool with no output schema, the description covers the data domain, scope, cost, and the full invocation protocol. The remaining gap is return shape and failure behavior, which is acceptable given the tool's simplicity but would help an agent planning multi-country queries.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point by explaining the purpose of the `payment` parameter in context — the first call yields terms, the second call with a signed payload completes the purchase. It also restates the 1-5 country scope, which the schema already carries.

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 exact data sources and indicators (World Bank labor market, unemployment, CPI inflation, GDP growth/per-capita, plus US Treasury rates and public debt) and the scope (1-5 countries), which is far more specific than the title 'Macro labor' alone. It stops short of an explicit verb like 'retrieve' and does not name a sibling to contrast against, but an agent can tell what it returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The payment protocol is spelled out as an explicit sequence: call once without `payment` for terms, sign with your own wallet, call again with `payment`. That removes the main ambiguity about when and how to invoke the tool. It gives no guidance on choosing this over sibling data tools, so it falls short of a 5.

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