Skip to main content
Glama

List Supported Brokers

tt_list_brokers
Read-onlyIdempotent

List brokers Tradetron is connected with.

country: 'IN' or 'US' to filter; None for both.

Use this for "what brokers do you support?" / "any US brokers?" Returns the distinct brokerages (distinct_brokers, the names to show users) and the counts. The per-route catalog rows (one per connection route, with each row's exchanges; ~44,000 characters for both countries) come back only with include_rows=true. For checking a specific broker by name use tt_check_broker_support — it's a deterministic match.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
countryNo'IN' or 'US' to filter; omit for both.
include_rowsNoFalse (default): the distinct brokerages and counts. True: also every catalog row (one per connection route, with exchanges).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds what they cannot: the default return shape (distinct_brokers, the names to show users, plus counts) versus the per-route catalog rows, and a concrete payload-size warning (~44,000 characters for both countries). That cost signal is exactly the kind of behavioral context an agent needs before setting include_rows.

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?

Front-loads the one-line purpose, then usage triggers, then return shape, then the alternative tool — a sensible order. Slightly repetitive since the country filter semantics are restated from the schema, and the multi-line return-shape paragraph 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?

There is no output schema, and the description compensates fully by explaining both return modes and their relative cost. For a two-parameter read-only listing tool, nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the field docs: it frames distinct_brokers as the user-facing names, and explains that include_rows expands to one row per connection route with each row's exchanges. The only redundancy is restating the country filter values already in the schema.

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 ('List brokers Tradetron is connected with') and immediately separates itself from the name-lookup sibling by naming tt_check_broker_support as the deterministic match tool. An agent can distinguish this from other broker tools 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 concrete triggering user utterances ('what brokers do you support?', 'any US brokers?') and explicitly routes per-broker name checks to tt_check_broker_support. It also warns that the full route catalog should only be pulled with include_rows=true, which functions as a when-not guideline for the expensive path.

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