FinChiefs research

Search macro views

search_macro_views

Read-only

Individual macro themes and drivers from provider research (growth, inflation, policy, fiscal, geopolitics, …), each with a description and a link to the source publication. Items come in pages (offset / next_offset), spread across providers by default. For counts and trends, call summarize_views first.

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

Input Schema

Name	Required	Description
`limit`	No	Items per page, at most 100. Default 100.
`order`	No	"spread" (default) interleaves providers so each page covers as many sources as possible; "newest" is strictly newest first.
`since`	No	Start date YYYY-MM-DD. Default: 30 days ago. The free plan reaches back 7 days for individual items.
`terms`	No	Subject words to match (assets, tickers, countries, central banks, companies, themes). Whole-word, case-insensitive; any term may match. Include synonyms and tickers, e.g. ["gold", "xau", "bullion"]. Omit to get everything in range. Matched against the theme name and description.
`until`	No	End date YYYY-MM-DD, inclusive. Default: today.
`offset`	No	Skip this many items; pass the previous response's next_offset to read the next page.
`category`	No	A macro category key from list_categories, e.g. "monetary_policy".
`provider_id`	No	Limit to one research provider (id from list_providers).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them by disclosing pagination mechanics (offset / next_offset) and the default cross-provider interleaving that shapes result ordering — context an agent would otherwise miss until it saw a response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each load-bearing: what the items are, how they page, and where to go instead for aggregates. The routing hint is front-loaded after the definition, and there is no filler.

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?

There is no output schema, but the description covers the essential return shape (each item has a description and a link to the source publication) and all 8 parameters are fully documented in the schema. Adequate for a filtered list tool, though it says nothing about response envelope fields such as next_offset location beyond naming it.

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 100%, so every parameter is already documented in the schema, including the spread vs newest order semantics and the free-plan 7-day limit. The description repeats the spread-by-default and offset/next_offset behavior but adds no syntax or usage nuance the schema lacks, so baseline 3 applies.

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 — individual macro themes and drivers from provider research — and enumerates the content types (growth, inflation, policy, fiscal, geopolitics). It does not explicitly contrast with search_asset_views or search_research, so sibling differentiation relies on the reader inferring 'macro' vs 'asset'.

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?

Explicitly routes the agent to summarize_views for counts and trends, which is a concrete when-to-use-elsewhere rule. It stops short of stating exclusions relative to the other search_* siblings or naming what to use when you want the underlying publications rather than themes.

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

All FinChiefs research 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.

Resources

Need Help?