Skip to main content
Glama

Broker Integration Guide

tt_broker_integration_guide
Read-onlyIdempotent

Deterministic, KB-grounded step-by-step for connecting a broker / webhook / data feed to Tradetron (TradingView/Chartink/API/virtual server). Serves stable steps from the curated KB feed instead of RAG; NEVER invents broker-specific steps. Call with NO arguments first when unsure of the topic: that returns mode:'index' — the full menu of ~24 curated topic ids (per-broker connect guides plus tradingview_webhook, chartink, generic_webhook_api, virtual_server, ...) with confirmed flags and the generic connect flow. A user asking about a 'static IP' means the virtual_server topic: Tradetron does not sell a static IP (NSE rules bar empanelled vendors from selling public IPs) and never call it one in the reply. Then pass topic = one id from that index, or free text in broker (broker name or mechanism). The topic list is data-driven — the index, not this docstring, is authoritative. For whether a broker is supported/connected use tt_check_broker_support / tt_list_brokers; for product how/why use tt_ask_tt — this tool is for SETUP procedures.

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

Input Schema

NameRequiredDescriptionDefault
topicNo
brokerNo

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, closed-world), and the description adds real behavioral context beyond them: it is deterministic and KB-fed rather than RAG, it never invents broker-specific steps, and the topic list is data-driven so the index rather than the docstring is authoritative. It also discloses the special no-argument return mode and a domain constraint (a 'static IP' request maps to virtual_server; Tradetron does not sell public IPs).

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 most important instruction — call with no arguments first and read the index — is front-loaded, and almost every clause carries operational value. It is dense and slightly run-on, with the static-IP aside and the 'topic list is authoritative' restatement adding bulk that could be trimmed, but nothing is redundant filler.

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?

For a two-optional-parameter, read-only tool with no output schema, the description covers what it needs: how to discover valid inputs, how to invoke it, what the degenerate no-arg call returns, and how to route support/product questions elsewhere. An agent can call it correctly on the first attempt.

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 0% and neither parameter has a schema description, so the description must carry the load — and it largely does, defining `topic` as one id from the returned index and `broker` as free text naming a broker or mechanism, presenting them as alternatives. It does not state what happens if both are supplied or how ambiguous free text in `broker` is resolved, so a small gap remains.

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 states a specific verb and resource: KB-grounded step-by-step setup procedures for connecting a broker, webhook, or data feed to Tradetron. It explicitly scopes itself to SETUP procedures and names the siblings that handle support status and product questions, so an agent can separate it from tt_check_broker_support and tt_ask_tt without opening a 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 gives an explicit invocation order ('Call with NO arguments first when unsure of the topic'), states what that call returns (mode:'index' with ~24 topic ids), and then the two ways to narrow down (topic id or free-text broker). It also names the alternatives and the exact condition that selects them: tt_check_broker_support / tt_list_brokers for support status, tt_ask_tt for product how/why.

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