Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

get_scanner_parameters

Retrieve available scanner parameters to configure market data filters for identifying trading opportunities through the Interactive Brokers API.

Instructions

Get available scanner parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the `get_scanner_parameters` tool, which uses `ib.reqScannerParametersAsync()` to fetch the data.
    if name == "get_scanner_parameters":
        params = await ib.reqScannerParametersAsync()
        return {"parameters_xml": params[:5000] + "..." if len(params) > 5000 else params}
  • Tool registration for `get_scanner_parameters` in the server definition list.
    Tool(
        name="get_scanner_parameters",
        description="Get available scanner parameters.",
        inputSchema={"type": "object", "properties": {}},
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify return format, whether results are cached, or what 'available' means (valid options vs current settings). Only the 'Get' verb implies a read operation.

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?

While the description is brief (4 words), the single sentence fails to earn its place by providing meaningful value beyond the function name. It is front-loaded but underspecified for the tool's purpose.

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 presence of run_scanner as a sibling and no output schema, the description should explain that this returns configuration metadata for the scanner. The absence of return value description and tool relationships leaves significant gaps.

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?

The tool accepts zero parameters, which per the evaluation guidelines sets a baseline score of 4. There are no parameters requiring semantic elaboration in the description.

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 available scanner parameters' is essentially a tautology of the function name, providing minimal additional clarity. It does not specify what 'scanner' refers to (market scanner), what the parameters control, or how it differs from run_scanner.

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 use this tool versus run_scanner or other data retrieval tools. It omits the crucial context that this should be called before run_scanner to determine valid parameter configurations.

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