Skip to main content
Glama

get_imf_weo_macro_snapshot

Read-only

Use when providing global macro context for an international expansion brief, country risk assessment, or board-level economic outlook presentation. Returns IMF WEO macro composites — GDP growth, inflation, and current account balance by country group. Example: Emerging market composite — GDP growth 4.2% vs advanced economy 1.7%, inflation diverging at 7.8% — growth premium exists but requires currency and political risk premium in discount rate. Source: IMF WEO static composite, semi-annual update. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover the safety profile (read-only, open-world, non-destructive), so the description earns credit for going beyond them: it discloses the upstream source, a semi-annual update cadence that signals data staleness risk, and a per-call cost of $0.02 USDC. It does not mention auth requirements or response granularity beyond 'by country group'.

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 the use case, followed by return contents, a worked example, and source/pricing metadata. The example sentence carries some interpretive commentary ('requires currency and political risk premium in discount rate') that illustrates downstream use rather than the tool itself, making it slightly longer than strictly necessary.

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?

With no parameters and no output schema, the description must carry the return-value burden, and it does: it names the three metrics, the country-group dimension, and gives sample magnitudes. It stops short of enumerating which country groups exist or the exact payload shape, but an agent has enough to call and interpret it.

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 no parameter meaning to convey and no schema gap to compensate for. Baseline of 4 applies; the description correctly implies the call is argument-free.

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 verb and resource: returns IMF WEO macro composites covering GDP growth, inflation, and current account balance broken out by country group. That is precise enough to distinguish it from generic macro siblings such as get_macro_market_signal, but it never explicitly contrasts itself with any named alternative.

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 opening clause gives concrete triggering contexts: international expansion briefs, country risk assessments, board-level economic outlook presentations. It is clear when to reach for it, but it offers no exclusions or guidance on when a different macro tool would be a better fit.

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