Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_historical_news

Retrieve historical news headlines for specific financial instruments using Interactive Brokers data. Specify contract ID and provider codes to access past market news.

Instructions

Get historical news headlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
con_idYesContract ID
provider_codesYesComma-separated provider codes
total_resultsNo

Implementation Reference

  • src/ib_async_mcp/server.py:791-806 (handler)
    The handler function that executes 'get_historical_news' using ib.reqHistoricalNewsAsync.
    if name == "get_historical_news":
    news = await ib.reqHistoricalNewsAsync(
        args["con_id"],
        args["provider_codes"],
        "",
        "",
        args.get("total_results", 10),
    )
    if news:
        return {
            "time": news.time.isoformat() if news.time else None,
            "provider_code": news.providerCode,
            "article_id": news.articleId,
            "headline": news.headline,
        }
    return {"error": "No news found"}
  • src/ib_async_mcp/server.py:411-422 (registration)
    The registration of 'get_historical_news' as a tool in the MCP server list_tools.
        name="get_historical_news",
    description="Get historical news headlines.",
    inputSchema={
        "type": "object",
        "properties": {
            "con_id": {"type": "integer", "description": "Contract ID"},
            "provider_codes": {"type": "string", "description": "Comma-separated provider codes"},
            "total_results": {"type": "integer", "default": 10},
        },
        "required": ["con_id", "provider_codes"],
    },
),

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

Zero annotations provided, so description carries full burden. 'Historical' implies past data but fails to disclose time range limits, pagination behavior, rate limits, or response format. No mention of data availability or caching.

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?

Extremely brief (4 words) and front-loaded, but undersized for a 3-parameter tool with no annotations. The single sentence states the obvious without earning its place through behavioral details or usage context.

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?

Insufficient for complexity level. With 3 parameters, no annotations, no output schema, and related siblings, the description should explain the contract-news relationship, provider code source, and return structure. Current description leaves significant gaps.

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 coverage is 67% (2 of 3 params described). Description adds no parameter context, but schema adequately covers con_id and provider_codes. total_results lacks description in schema and description provides no compensation for this gap.

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?

States clear verb ('Get') and resource ('historical news headlines'). 'Headlines' distinguishes from sibling 'get_news_article' (likely full articles), though it doesn't explicitly note this is contract-specific via con_id parameter.

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 guidance on when to use vs alternatives like 'get_news_article' or 'get_news_providers'. Does not mention prerequisite steps (e.g., obtaining provider codes via get_news_providers) or when historical vs current news is appropriate.

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