Skip to main content
Glama

Check Broker Support

tt_check_broker_support
Read-onlyIdempotent

Check whether Tradetron is connected with a given broker.

Deterministic lookup against the bundled broker catalog (sanitized snapshot of TT's brokers table — active integrations only). Use this BEFORE answering any "do you support broker X?" / "can I trade through Y?" question — it is authoritative. Do NOT guess from training data; if a broker is not in this catalog, Tradetron is not connected with it.

Matching is case-insensitive and whitespace-insensitive ('5paisa', '5 Paisa', '5Paisa' all collapse to one key). Substring matches also surface — 'kotak' returns every Kotak variant.

Returns: supported: True if at least one match exists. matches: broker rows (name, country, exchanges). message: one-liner safe to relay to the user. synthesis_instructions: guidance for you, not text for the user. resolved_from_alias: set when a common name ('IBKR', 'Angel Broking') was resolved to the catalog's own name.

Common abbreviations and former names are recognised ('IBKR', 'Angel Broking'). A partial-name match counts as supported ('kotak' matching Kotak Neo = YES). When supported=False, phrase it as "not currently integrated" and offer a live agent to raise the request — never a flat "no". When supported=True but tt_broker_integration_guide has no curated steps, it is still supported — offer a live agent to get the user connected.

For listing all supported brokers (e.g. "what brokers do you support in the US?") use tt_list_brokers instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "tt_check_broker_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses matching behavior (case-insensitive, whitespace-insensitive, substring matches surface), alias resolution ('IBKR', 'Angel Broking'), data provenance (sanitized snapshot, active integrations only), and even how to phrase a negative result ('not currently integrated' plus live-agent offer, never a flat 'no'). That is substantial operational context annotations cannot carry.

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?

Core purpose and the pre-answer directive are front-loaded, and the return-field breakdown plus phrasing rules are useful rather than filler. It runs longer than strictly necessary, with some line-broken formatting and prompt-style exhortations that could be tightened.

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

Completeness5/5

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

No output schema exists, yet the description enumerates the returned fields (supported, matches, message, synthesis_instructions, resolved_from_alias) and explains what synthesis_instructions is not to be relayed to the user. Combined with negative-result handling and alias behavior, an agent has everything needed to call and interpret it correctly.

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

Parameters5/5

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

Schema coverage is 0% with a single 'name' parameter, so the description must carry the burden — and it does, specifying that '5paisa', '5 Paisa' and '5Paisa' collapse to one key, that partial names count ('kotak' matching Kotak Neo = YES), and that legacy/common names resolve via resolved_from_alias.

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

Purpose5/5

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

States a specific verb and resource ('Check whether Tradetron is connected with a given broker') and explicitly names the sibling to use instead for listing ('use tt_list_brokers instead'). An agent can distinguish it from tt_list_brokers and tt_broker_integration_guide without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use this BEFORE answering any "do you support broker X?" / "can I trade through Y?" question'), an explicit prohibition ('Do NOT guess from training data'), and an explicit alternative for the adjacent task ('For listing all supported brokers ... use tt_list_brokers instead').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources