Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

get_news_article

Retrieve specific news articles from financial providers to support market analysis and trading decisions within the Interactive Brokers ecosystem.

Instructions

Get a news article.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_codeYes
article_idYes

Implementation Reference

  • The handler logic for the 'get_news_article' tool, which uses ib.reqNewsArticleAsync to fetch the article.
    if name == "get_news_article":
        article = await ib.reqNewsArticleAsync(args["provider_code"], args["article_id"])
        return {"article_type": article.articleType, "text": article.articleText}
  • The definition and registration of the 'get_news_article' tool with its input schema.
    Tool(
        name="get_news_article",
        description="Get a news article.",
        inputSchema={
            "type": "object",
            "properties": {
                "provider_code": {"type": "string"},
                "article_id": {"type": "string"},
            },
            "required": ["provider_code", "article_id"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. While 'Get' implies a read-only operation, the description omits response format, rate limits, authentication requirements, and error handling for invalid article IDs.

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

Conciseness2/5

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

While the description is brief (three words), it exemplifies under-specification rather than effective conciseness. The single sentence wastes no words but also provides zero informational value beyond the tool name itself.

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

Completeness2/5

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

Given the financial/trading context of sibling tools and the specific ID-based retrieval pattern, the description inadequately prepares the agent. With no output schema, the agent receives no indication of what article fields (headline, body, timestamp) are returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description completely fails to compensate. It describes neither the 'provider_code' format (is it a ticker? news source identifier?) nor the 'article_id' structure, leaving both critical parameters undocumented.

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

Purpose2/5

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

The description 'Get a news article' is tautological and restates the tool name without adding specificity. It fails to distinguish this tool from sibling 'get_historical_news' (which retrieves multiple articles) or clarify what constitutes valid provider codes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance provided. The description does not indicate when to use this specific retrieval endpoint versus 'get_historical_news' or 'get_news_providers', nor does it mention prerequisite steps like obtaining article IDs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nadavgb-atom/ib-async-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server