Skip to main content
Glama
aiordanescu

ib-gateway-mcp

by aiordanescu

Stream news headlines

subscribe_news
Read-only

Stream live news headlines for a specific instrument or an entire provider feed. Get a subscription handle to read headlines and fetch full stories, then cancel when done.

Instructions

Stream live news headlines for one instrument, or a provider's whole feed.

Give a contract for headlines about that instrument (from provider_code, or every
subscribed provider), or only a provider_code for that provider's broad tape (all
its headlines, e.g. BRF for Briefing Trader, BZ for Benzinga, FLY for The Fly;
each needs its own subscription). Returns a handle; read the headlines (oldest
first, the newest 200 kept) with get_subscription_data(subscription_id) and fetch
a full story with get_news_article. Uses one market data line. Stop it with
unsubscribe; it is cancelled after idle_ttl_s seconds without a read.
Errors: invalid_request without a contract or provider_code, or when a contract is
given with a provider the login is not subscribed to (see get_news_providers);
ib_api_error when IBKR refuses the stream (no news permission for that provider).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractNoThe instrument whose headlines to stream (a con_id alone is unambiguous). Omit to stream a provider's whole feed instead.
provider_codeNoProvider code. With a contract: only this provider's headlines (default: every subscribed provider). Without a contract: that provider's whole feed (broad tape), e.g. BRF, BZ or FLY.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesWhat it streams for: the contract id plus parameters.
kindYesWhat streams: quotes, depth, tick_by_tick, realtime_bars, bars, scanner, news_bulletins, news or display_group.
contractNoThe instrument, when there is one.
created_atYes
idle_ttl_sYesSeconds without a read before it is cancelled.
deduplicatedNoTrue when an identical stream was already open and its handle was returned instead of opening a second one.
subscription_idYesHandle for get_subscription_data and unsubscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the subscription lifecycle: it returns a handle, keeps the newest 200 headlines, requires reads via get_subscription_data, consumes one market data line, cancels after idle_ttl_s, and reports specific error conditions. This is exactly the kind of behavioral context agents need.

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?

The description is dense but well structured: purpose first, then invocation modes, consumption, teardown, and errors. Every sentence carries operational meaning, and the most important decision — contract versus provider_code — is front-loaded.

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?

The description covers setup, consumption, story retrieval, unsubscription, retention limits, resource usage, and failure modes. Given the output schema exists and the annotations are present, nothing essential is missing for an agent to call and manage this subscription 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% and the schema descriptions already explain contract and provider_code. The description adds value by giving concrete provider examples, noting that each provider feed needs its own subscription, and linking errors to provider subscription status via get_news_providers.

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 first sentence states a specific action and resource: 'Stream live news headlines for one instrument, or a provider's whole feed.' The two modes, instrument-specific versus provider-wide feed, are clear and help distinguish this from related news tools such as get_historical_news, get_news_article, and subscribe_news_bulletins.

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?

The description clearly explains when to pass a contract versus only a provider_code, gives concrete examples, and names downstream tools for reading, fetching stories, and unsubscribing. It does not explicitly contrast with subscribe_news_bulletins or historical news, but the 'live' qualifier and references to alternatives make the intended usage inferable.

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