Skip to main content
Glama

My Connected Brokers

tt_get_my_brokers
Read-onlyIdempotent

The brokers connected on the user's own Tradetron account, per exchange — the set tt_deploy_strategy_paper picks from.

Use it before a deploy to tell the user which of their brokers the deployment will sit on (their primary broker where it is connected, otherwise the first connected one), and whether any exchange the strategy trades has none — a deploy there refuses. This is a read: it cannot connect a broker. Connecting one needs the user's own broker login on Tradetron — give them connect_url; never ask for broker credentials in chat. A broker in brokers_without_exchange IS connected, but Tradetron holds no exchange for it, so a deploy from here cannot attach it; connected_without_exchange names the ones that may trade a missing exchange. Never tell the user to connect a broker they already have.

AUTH-REQUIRED: needs a per-user Tradetron connection.

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_get_my_brokers"
  }
}

Input Schema

NameRequiredDescriptionDefault
exchangesNoOptional exchange codes to check, e.g. ['NFO', 'DELTAINDIA']. Adds missing_exchanges: the ones with no connected broker, where a deploy would refuse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantive behavior: it explicitly cannot connect a broker, has an auth requirement per user, selects the primary broker where connected and otherwise the first connected one, and disambiguates `brokers_without_exchange` (connected but no exchange held) from `connected_without_exchange`. It even guards against a likely agent error by warning not to tell a user to connect a broker they already have.

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?

The content is front-loaded: identity of the resource and its consumer come first, then the pre-deploy usage, then behavioral caveats, then auth. It is longer than typical but nearly every clause carries decision-relevant information; the closing 'never tell the user to connect a broker they already have' restates an implication of the preceding sentences and is the one mild redundancy.

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

Completeness4/5

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

With no output schema, the description carries the return contract and does so well for the decision at hand: it names `missing_exchanges`, `brokers_without_exchange`, `connected_without_exchange`, and `connect_url`, plus the primary-broker selection rule. It stops short of describing the full shape of each broker entry (identifiers, display fields, ordering), which is a minor gap given the pre-deploy purpose it declares.

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?

The single `exchanges` parameter is fully documented in the schema, including the example codes and the resulting `missing_exchanges` field, so the schema does the heavy lifting. The description reinforces the deploy-refusal consequence of a missing exchange but adds no syntax or format detail beyond what the schema already provides.

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?

The description names a specific resource with scope: the brokers connected on the user's *own* Tradetron account, per exchange, and ties it directly to tt_deploy_strategy_paper as the set that tool picks from. That scope word ('own') is what separates it from sibling list tools like tt_list_brokers, so an agent can choose correctly without opening either 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?

It states the trigger explicitly ('use it before a deploy') and the decision it feeds (which broker the deployment sits on, and whether any traded exchange has none, where a deploy refuses). It also gives exclusions and alternatives: this tool cannot connect a broker, connecting needs the user's own Tradetron login via `connect_url`, and credentials must never be requested in chat.

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