Skip to main content
Glama

Helious market intelligence

The Helious feed

get_feed
Read-onlyIdempotent

The Helious feed, newest first: the posts Helious publishes (kind post: releases with their surprise, auction results, board updates, the daily brief and live squawk lines) and the wire headlines it carries (kind headline: breaking news, geopolitics, official statements, central bank speakers, bank and business notes). Every item has a stable id, and items carry two score channels on a -10 to +10 scale: score and direction for bonds, equity_score and equity_direction for stocks. The same story can be bullish for bonds and bearish for stocks, so read the channel you trade. topic is what the item is about, the code the terminal prints on the row (equities, bonds, cb, geo, data, chatter); category is only the lane it came in on, so a stock story off the news wire has category news and topic equities. Most items carry helious_read, Helious's plain-English line on why it matters. A headline also carries carried_at (when Helious put it on the tape; created_at is when it was published) and a URL-free thread_id that stays the same when a story is retitled. No headline names its outlet, author or link. Depth follows the connected account for the permanent posts: releases, auctions, desk posts, the brief, the minutes. Headlines are kept 7 days whatever the plan (official statements and Fed speakers 400 days), as are squawk lines and the board lanes. Optional q filters by word; categories narrows to chosen lanes; kind narrows to headline or post; topics narrows to what items are about; since moves the window's start later. The filters search the whole window and matched counts every match. Where the account receives news an hour behind: a post from created_at, a headline from the later of created_at and carried_at. A headline names no outlet as its source: a trailing ' - Outlet', a 'via Outlet' credit and the wire's label are removed; a headline about an outlet, or about an index such as the Nikkei, can still mention one.

Input Schema

NameRequiredDescriptionDefault
qNoFilter word.
kindNoheadline or post. Empty means both.
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 items to return.
sinceNoOnly items published at or after this date (2026-10-30) or ISO 8601 time; never earlier than the plan's history (plan_limit says so when it asks for more). Empty, or a value that is not a date, means the whole window.
topicsNoComma-separated topics, like equities or bonds,cb: what the item is about, the terminal's row code. Matches the topic or the secondary_topic. One of cb, geo, bonds, data, equities, chatter, desk, narrative, energy, fx. Empty means all.
categoriesNoComma-separated lanes, like release,auction or news,geo. Empty means all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Only items published at or after this date (2026-10-30) or ISO 8601 time; never earlier than the plan's history (plan_limit says so when it asks for more). Empty, or a value that is not a date, means the whole window.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / topics
      Added value: +{
      +  "description": "Comma-separated topics, like equities or bonds,cb: what the item is about, the terminal's row code. Matches the topic or the secondary_topic. One of cb, geo, bonds, data, equities, chatter, desk, narrative, energy, fx. Empty means all.",
      +  "type": "string"
      +}
  3. 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."
  4. Changed2 schema fields changed
    • changedInput schema / properties / categories / description
      Previous value: -"Comma-separated lanes, like release,auction. Empty means all."New value: +"Comma-separated lanes, like release,auction or news,geo. Empty means all."
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "headline or post. Empty means both.",
      +  "type": "string"
      +}
  5. 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"
      +}
  6. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description goes far beyond them: it discloses the one-hour news delay and the 5-credit fresh override, retention windows per content type, depth tied to the connected account, outlet-name stripping, and the stable id/thread_id behavior. That is unusually rich behavioral context with no contradiction.

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 purpose is front-loaded and most sentences carry useful detail, but the whole definition is a single dense paragraph. The outlet-anonymization rule is stated twice (once as 'No headline names its outlet, author or link' and again at length at the end), which is avoidable repetition.

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

Completeness5/5

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

For a 7-parameter, zero-required feed tool with no output schema, the description is complete: it covers what is returned, the two score channels, per-plan depth, retention, filter behavior, delay/fresh economics, and source anonymization. An agent has enough to call it correctly.

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?

Schema coverage is 100%, so baseline is 3. The description earns above baseline by explaining the topic-versus-category distinction with a concrete example (a stock story off the wire has category news and topic equities), and by noting that filters search the whole window and matched counts every match.

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 resource (the combined Helious feed) and enumerates what it contains: posts (releases, auction results, board updates, brief, squawk) and headlines. An agent can tell this is the general feed rather than a specialized endpoint, but it never names or routes against siblings like get_auctions or get_squawk_sessions.

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?

Usage is strongly implied by the content description and the filter semantics (q, categories, kind, topics, since), and the fresh/delay tradeoff is explained. However, there is no explicit when-to-use guidance versus the many specialized sibling tools, and no exclusions or alternatives are named.

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