BeliefState

Get macroeconomic context

get_macro_context

Retrieves retained government macroeconomic observations in one ticker research scope. Filter by native series_ids, agency, measurement_names and period dates; returns typed values, units, seasonal bases, scales, native periods and source support. Supported archive formats cover Treasury, NY Fed, BLS, BEA, EIA, CFTC and metadata-qualified Federal Reserve Board series; other admitted context is explicitly bounded. Macro backdrop does not establish company exposure or a historical data vintage; FRED and rights-held series are unavailable. Current requests recheck stale mirror metadata; historical/pinned reads remain fixed. Continue with the returned snapshot, cutoff, filters and cursor or next_offset. Uses account allowance or prepaid credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_macro_context"
  }
}

Input Schema

Name	Required	Description
`as_of`	No	Availability cutoff, separate from event/period filters. Historical reads never refresh.
`limit`	No	Matching typed observations per page; default32.
`agency`	No
`cursor`	No	Archive continuation token; reuse with snapshot ID/hash, as_of and unchanged filters.
`offset`	No
`ticker`	Yes
`context`	Yes	User's research goal in one short sentence (max 300 characters); include relevant ticker and topic. Exclude names, contact/account/portfolio details, credentials and source text.
`date_to`	No	Inclusive native date upper bound, selected by date_field.
`date_from`	No	Inclusive native date lower bound, selected by date_field.
`llm_model`	Yes	Your model identifier, if known (e.g. gpt-6); otherwise leave unknown. Exclude credentials and private deployment names.
`date_field`	No	Date meaning; defaults to period for facts/macro/holdings/returns, event for insider trades, observation for options/short volume, scheduled for calendar.
`series_ids`	No
`snapshot_id`	No	Pin continuation to the returned snapshot ID; reuse with snapshot_hash and as_of.
`snapshot_hash`	No
`filters_sha256`	No	Reuse the returned filter hash unchanged with continuation pages.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
`measurement_names`	No	Exact native measurements, such as a Treasury maturity column.
`max_snapshot_age_hours`	No	Requested verification-age tolerance: default1hour for retained archives,24hours for closing-price references. Record dates and publication cadence are separate.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations, it discloses credit consumption, that current requests recheck stale mirror metadata while pinned/historical reads stay fixed, and that continuation requires the returned snapshot, cutoff, filters and cursor/offset. This is meaningful side-effect and freshness context. It does not quantify rate limits or page-size behavior beyond what the schema already states.

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?

Content is front-loaded with purpose, then filters, format coverage, limitations, continuation, and billing — a sensible order with no filler sentences. The telegraphic phrasing ('Macro backdrop does not establish company exposure or a historical data vintage') is terse to the point of needing rereads.

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 an 18-parameter retrieval tool with an output schema, the definition covers scope, supported archives, exclusions, freshness semantics, continuation, and cost. The remaining gaps (per-parameter guidance for ticker/snapshot_hash, explicit sibling routing) are modest rather than blocking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is about 72%, so some compensation is needed. The description names the main filters (series_ids, agency, measurement_names, period dates, snapshot, cursor/offset) and thus covers several parameters that lack schema descriptions, but it does not explain ticker constraints, snapshot_hash usage, or the distinction between offset and cursor in any detail.

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 opening sentence names a specific verb (Retrieves), resource (retained government macroeconomic observations) and scope (one ticker research scope), and adds the returned field set. It does not name a sibling such as get_economic_calendar or get_company_facts, so the boundary with adjacent context tools is implied rather than stated.

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?

It sets useful boundaries — FRED and rights-held series are unavailable, and macro backdrop does not establish company exposure — which tells the agent when this tool will fail or mislead. It never explicitly routes to an alternative sibling (e.g., calendar-type events or company facts), so the when-to-use-vs-alternatives guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BeliefState tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.