Skip to main content
Glama

Stratalize Intelligence

Get Macro Playbook

get_macro_playbook
Read-only

Use when a trader or portfolio manager needs current regime label and tactical positioning. Returns active regime, verifiable FOMC facts, live market snapshot, model interpretation, concurrent playbooks, and key levels. Example: regime label with playbook actions and risk triggers. $0.50 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_macro_playbook"
  }
}

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds information annotations cannot carry: the exact return bundle (regime, FOMC facts, live snapshot, interpretation, levels) and, critically, the $0.50 USDC per-call cost, which is essential for an agent deciding whether to invoke. It stops short of stating data freshness, caching, or per-call failure modes, so a 4 rather than 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?

Four sentences, front-loaded with the usage trigger, then returns, then example, then price. Nothing is padded, but the "Example: regime label with playbook actions and risk triggers" restates the preceding returns list without adding a scenario, so it is slightly redundant.

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 input parameters and no output schema, the description must carry the burden of explaining return contents, and it does so by enumerating six payload components. Cost is disclosed. Minor gaps remain: whether the snapshot is real-time or delayed, and what "concurrent playbooks" actually means in practice.

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; the baseline for 0 params is 4. The description correctly implies a parameterless, one-shot fetch by not referencing any inputs.

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 states a specific verb (get) and resource (macro playbook), then enumerates what the payload contains: active regime, FOMC facts, live market snapshot, model interpretation, concurrent playbooks, and key levels. An agent can tell this is a macro-regime/positioning report. It does not explicitly differentiate from siblings such as get_macro_market_signal or get_imf_weo_macro_snapshot, so it falls short of a 5.

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?

"Use when a trader or portfolio manager needs current regime label and tactical positioning" gives a clear trigger condition and audience. There are no explicit exclusions or named alternatives to steer the agent away when it wants a raw data snapshot rather than an interpretive playbook, so it is clear context without routing guidance.

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