Skip to main content
Glama

Stratalize Intelligence

Get Imf Weo Macro Snapshot

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 declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: the data source is a static IMF WEO composite updated semi-annually, no inputs are needed, and each call costs $0.02 USDC — the cost and data-vintage details are the most valuable disclosures here.

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?

It is front-loaded with the 'Use when' trigger, then moves to returned content, a worked example, provenance, and price — a sensible order with no filler. The illustrative example sentence is the longest element and is somewhat verbose, but it conveys the shape of the output.

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, read-only tool with no output schema, the description covers trigger context, payload contents, source, update cadence, and cost — enough for an agent to decide and call correctly. It could still be clearer on how many country groups are covered, but nothing essential is missing.

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 and there is no parameter semantics to explain. The description correctly implies a parameterless snapshot call rather than promising filters that do not exist.

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 and its contents: IMF WEO macro composites with GDP growth, inflation, and current account balance broken out by country group. That is far more specific than the title, but it never positions itself against similar siblings such as get_macro_market_signal or get_macro_playbook, so an agent must infer which macro tool to pick.

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 'Use when...' clause gives three concrete triggering scenarios (international expansion brief, country risk assessment, board-level economic outlook), which is clear usage context. It stops short of exclusions or naming an alternative tool for adjacent macro needs.

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