Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_news_providers

Retrieve available news providers for market data access through the Interactive Brokers API.

Instructions

Get available news providers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/ib_async_mcp/server.py:783-786 (handler)
    The handler logic for "get_news_providers" which calls ib.reqNewsProvidersAsync() and formats the output.
    if name == "get_news_providers":
    providers = await ib.reqNewsProvidersAsync()
    return [{"code": p.code, "name": p.name} for p in providers]
  • src/ib_async_mcp/server.py:393-397 (registration)
    The Tool definition/registration for "get_news_providers" in the list of tools.
    Tool(
    name="get_news_providers",
    description="Get available news providers.",
    inputSchema={"type": "object", "properties": {}},
),

Tool Definition Quality

B3/5.0
Behavior2/5

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

No annotations provided, so the description carries full disclosure burden. It only states the basic retrieval action without describing return format, whether results are cached, or that this is a prerequisite discovery call for other news tools. It implies read-only behavior but lacks essential behavioral context.

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?

Extremely concise at four words with no wasted language. However, the brevity borders on under-specification given the tool's role in the broader news workflow; a single additional clause about its relationship to other tools would improve utility without sacrificing structure.

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?

Lacks necessary context for a discovery endpoint with no output schema. Given siblings `get_news_article` and `get_historical_news`, the description should explain that this returns provider identifiers used as input parameters for those other functions. Without this, the agent cannot understand the operational workflow.

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?

Zero parameters present, establishing baseline 4 per rubric guidelines. With an empty input schema, there are no parameter semantics to describe beyond confirming none are required, which the description implicitly conveys through its simplicity.

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 verb (Get) and resource (available news providers), clearly indicating it retrieves a list of news sources. However, it fails to differentiate from siblings like `get_news_article` and `get_historical_news`, which also operate on news data.

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 provided on when to invoke this tool versus other news-related functions. Given the presence of `get_historical_news` and `get_news_article`, the description should indicate this is typically called first to discover valid provider IDs for subsequent filtering.

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