Skip to main content
Glama

List my linked brokerages

list_brokerages
Read-onlyIdempotent

YOUR brokerages linked to Gambit through SnapTrade (requires api:portfolio). connected is true when any link is active; connections lists each link: id (pass it to unlink_brokerage), brokerageName, brokerageSlug, disabled (the link needs a re-login at the broker), brokerCanTrade and canTrade (whether that link can place orders; this tool only reads, and stock orders go only through propose_stock_order and confirm_stock_order, which need the api:stock_trade scope and are admin-only and off by default). Connection ids are not account ids: propose_stock_order takes get_holdings accounts[].accountId. Holdings and cash: get_holdings. Link a new brokerage: start_brokerage_connect.

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": "list_brokerages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only/idempotent/non-destructive, but the description adds material context beyond them: the api:portfolio scope requirement, the meaning of connected/disabled, the brokerCanTrade vs canTrade distinction, and that the trading path requires api:stock_trade and is admin-only and off by default. That is exactly the kind of authorization and state semantics annotations cannot express.

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-loaded and free of filler — every clause carries information. However, it is one long run-on paragraph with nested parentheticals, so the navigation cues ("Holdings and cash:", "Link a new brokerage:") are buried rather than visually separated.

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?

With no output schema, the description must explain the shape of the response, and it does so field by field with semantics for each flag. For a zero-argument read tool it covers everything an agent needs: scope, return shape, id usage, and next-step tools.

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 takes zero parameters, so the baseline is 4; there is nothing in the input schema to clarify. The description instead documents the response field names (id, brokerageName, brokerageSlug, disabled, brokerCanTrade, canTrade), which is useful but is return-value rather than parameter semantics.

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?

Opens with a specific verb+resource+scope: "YOUR brokerages linked to Gambit through SnapTrade," and names the required scope (api:portfolio). It is immediately distinguishable from list_* siblings and from account-oriented tools like get_holdings.

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?

Explicitly routes the agent: holdings and cash go to get_holdings, linking a new brokerage goes to start_brokerage_connect, removing a link goes to unlink_brokerage, and order placement goes to propose_stock_order/confirm_stock_order. It even pre-empts the common confusion that connection ids are order inputs.

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