Skip to main content
Glama
nadavgb-atom

ib-async-mcp

by nadavgb-atom

search_symbols

Find matching financial instruments by entering a search pattern to identify symbols or contracts for trading and market analysis.

Instructions

Search for matching symbols/contracts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesSearch pattern

Implementation Reference

  • The 'search_symbols' tool handler, which uses 'ib.reqMatchingSymbolsAsync' to search for symbols based on a pattern.
    if name == "search_symbols":
        results = await ib.reqMatchingSymbolsAsync(args["pattern"])
        return [serialize_object(r) for r in (results or [])]
  • The 'search_symbols' tool definition, including its input schema requiring a 'pattern' string.
    Tool(
        name="search_symbols",
        description="Search for matching symbols/contracts.",
        inputSchema={
            "type": "object",
            "properties": {
                "pattern": {"type": "string", "description": "Search pattern"},
            },
            "required": ["pattern"],
        },
    ),
Behavior2/5

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

No annotations provided, yet the description discloses no behavioral details: it doesn't state what the search returns (list of contracts? symbols?), matching logic (substring, exact, regex), or if the operation is idempotent/safe.

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 single sentence with no fluff or redundancy. However, the brevity contributes to under-specification rather than efficient communication of necessary details.

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?

Inadequate for a financial trading API with complex contract types. Lacks explanation of return format, pagination, or how results differ from related contract tools. With no output schema and no annotations, the description should carry more explanatory burden.

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 100% for the single 'pattern' parameter. The description mentions 'matching' but adds no specific semantics about pattern syntax (e.g., glob vs. regex) or valid formats beyond what the schema already provides.

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

Purpose3/5

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

States the basic action (search) and resource (symbols/contracts) but is somewhat tautological with the tool name. Critically, it fails to distinguish from siblings like 'qualify_contracts' or 'get_contract_details' which also deal with contract resolution/validation.

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 versus 'qualify_contracts', 'get_option_chain', or 'get_contract_details'. No mention of search syntax (wildcards, partial matching) or prerequisites.

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