Skip to main content
Glama
Sign In

Helious market intelligence

by io.helious
OverviewDiscussionsAdmin

FOMC minutes and speech digests

get_document_digests
Read-onlyIdempotent

The desk's read of FULL central bank documents, not headlines: FOMC minutes and Fed/ECB speeches read end to end. Each digest carries a summary, what is genuinely new versus what the market already knew, key findings with their market consequence, a hawkish/dovish committee lean, and quotes verified word for word against the source document. Minutes carry no bond or equity direction on purpose: they describe a meeting about three weeks earlier, so the desk states the lean and declines the market call. Delayed 60 minutes where the account receives news an hour behind.

Input Schema

NameRequiredDescriptionDefault
kindNominutes, speech, or all (default).
freshNoSet true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key.
limitNoMost digests to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key."New value: +"Set true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key."
  2. Changed1 schema field changed
    • addedInput schema / properties / fresh
      Added value: +{
+  "description": "Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive open-world call. The description adds substantial behavior beyond annotations: digest fields, source-verified quotes, the deliberate absence of market direction in minutes, and the 60-minute delayed account behavior.

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?

The description is front-loaded with the core purpose and remains reasonably compact for the tool's complexity. A few phrases, such as repeated emphasis on full documents versus headlines, could be tightened, but the content largely earns its place.

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 usefully summarizes what each digest contains and notes the delayed-news behavior. It does not fully describe output shape or pagination, but the schema covers the parameters and the remaining gaps are minor.

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 kind, fresh, and limit are already documented in the input schema. The description does not add parameter-specific syntax or defaults beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: it returns the desk's read of full FOMC minutes and Fed/ECB speeches, not headlines. It also enumerates the digest contents, so an agent can distinguish this from market-data siblings without opening the schema.

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 implies when to use the tool by contrasting full-document digests with headlines, and it explains why minutes omit bond or equity direction. However, it does not explicitly name alternatives such as get_feed or state when not to use this tool, leaving routing guidance partly inferred.

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

All Helious market intelligence toolsInspect
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