Skip to main content
Glama

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

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description adds value beyond them by enumerating the returned payload (regime, verifiable FOMC facts, live market snapshot, interpretation, concurrent playbooks, key levels) and disclosing the $0.50 USDC cost per call. The payment mechanism is only vaguely indicated and no rate limits or freshness guarantees are stated, which keeps it below 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?

Three sentences, front-loaded with the trigger condition, then the return contents, then pricing, which is a sensible order. The 'Example:' sentence largely restates the return list already given and is somewhat redundant, costing a bit of tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description carries the full burden of explaining what comes back, and it does list six return components plus cost. Still missing is any indication of data freshness, latency, or what the payload looks like structurally, which matters for a live market tool. The addition of payment mechanism detail would also improve completeness.

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 and the schema is an empty object, so no parameter semantics are needed and the description is not expected to explain any. The baseline for a zero-parameter tool applies, with no penalty since nothing is undocumented.

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-plus-resource: it returns an active regime label with tactical positioning and playbook actions. It is clear enough to distinguish from a generic market-signal tool, but it never names or contrasts any sibling such as get_macro_market_signal or get_imf_weo_macro_snapshot, so sibling differentiation is absent.

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?

There is an explicit trigger ('Use when a trader or portfolio manager needs current regime label and tactical positioning'), which is better than nothing. However, there is no guidance on when not to use it, no prerequisites, and no routing to the obvious alternative macro tools, so usage is only partially covered.

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