FinChiefs research

Get daily digest summaries

get_daily_digests

Read-only

The Daily Digest: one synthesis per day per category (e.g. gold, oil, us_bonds, top macro themes, policy_makers), written from all providers' views that day — the read, why, sub-splits, individual names, where providers appear to disagree — with the day's code-computed tallies, structured highlights (consensus by asset, apparent disagreements with each side's horizon and condition, notable names) and, where it exists, a short note on how the read evolved over the previous two weeks. Best for the picture on a market and how it moved day by day. Category keys (has_daily_digest) come from list_categories.

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": {
      "categories": "<categories>"
    },
    "name": "get_daily_digests"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Digests per page, at most 100. Default 30.
`since`	No	Start date YYYY-MM-DD. Default: 14 days ago. The free plan reaches back 7 days.
`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.
`categories`	Yes	Category keys, e.g. ["gold"] or ["top", "policy_makers"]. "__overall__" is the cross-asset summary.

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 only declare readOnlyHint and openWorldHint=false; the description adds substantive context about what the response actually contains, including structured highlights and a two-week evolution note. It does not discuss pagination mechanics or auth requirements, but the schema already covers the paging parameters.

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

Conciseness3/5

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

The description is front-loaded with the core idea, but it is one sprawling sentence whose long inventory of digest contents becomes dense and hard to scan. The content is relevant, yet it could be broken into a short purpose sentence plus a structured list without losing meaning.

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 output schema, the description carries the burden of explaining return values, and it does so thoroughly by describing the digest's composition and highlights. Paging behavior is left to the schema, which is acceptable, but the description could more explicitly indicate the response envelope shape.

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 description coverage is 100%, so the parameters are already well documented. The description adds only a modest amount of meaning beyond the schema: the per-category nature of the resource and the pointer to list_categories for valid keys, which the schema partially implies with its examples and '__overall__' note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (a daily, per-category synthesis built from all providers' views) and enumerates its contents: the read, why, sub-splits, names, disagreements, tallies, and structured highlights. An agent can distinguish this from search_asset_views or summarize_views, which return raw or summarized views rather than a per-day per-category digest.

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?

It gives a clear when-to-use signal — 'Best for the picture on a market and how it moved day by day' — and tells the agent where category keys come from (list_categories, has_daily_digest). It does not name explicit alternatives or when-not-to-use conditions, which keeps it short of a 5.

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?