Skip to main content
Glama

Create Signal Bridge (webhook-driven template)

tt_create_signal_bridge

Build a WEBHOOK-DRIVEN multi-symbol strategy ("Signal Bridge") for a basket, create it in the user's account, link its API token in HYBRID mode, and return everything needed to drive it from outside.

Use when the user wants to trade from THEIR OWN signals (their code, TradingView, a PMS/advisory feed, a WL partner) rather than Tradetron conditions: "send BUY/SELL from my python", "signal-driven portfolio", "API-linked template", "PMS basket with webhook signals".

What the template does (one Long + one Short set per symbol, one python block): accepts = BUY / BUY EXIT / SELL / SELL EXIT via the webhook; rejects invalid signals with a reason (_msg); sizes by Fix / Capital % / Capital Risk % / Allocation Method 1; per-trade target & SL (money/points/%); master target/SL with reset; max open positions; max capital per symbol; working days; session window; intraday square-off; square-off-all on TP/SL; futures/options expiry-day exit. Every setting is a runtime variable the webhook can change while live.

OPTIONS: an option item is a relative rule (CE/PE, strike steps from ATM SPOT, expiry label) resolved when a BUY/SELL is accepted; the strike is pinned for that entry and the exit closes the contract that was entered. Its variable is <CE|PE><ATM|ATMP|ATMM> plus _NW/_CM/_NM when the expiry is not the underlying's default (Current Week for NIFTY 50/SENSEX, Current Month otherwise) — e.g. NIFTY50_CE_ATM, NIFTY50_PE_ATMM1, NIFTYBANK_CE_ATMP2. SELL writes the option (needs the broker's writing margin; size shorts with Fix lots).

CONFIRM the basket and exchange with the user first (it creates a template). Returns template_id, view_url, api_link (hybrid state), auth_token (the user's own webhook credential: anyone holding it can send signals to this template), python_client (copy-and-run: sends one real BUY), curl_example, signal_links (four ready GET links per variable: BUY / BUY EXIT / SELL / SELL EXIT — a plain link works), guide_markdown (the full client guide), variable_reference, capabilities (built / built differently / not possible, with reasons), next_steps. Give the user python_client unchanged (it carries their token: hand it over once and do not repeat the token in later replies). If api_link.hybrid_applied is false, tell the user to set Hybrid Mode = Yes before deploying (steps are included).

It does not deploy. Tell the user how to deploy it: Live Offline (Tradetron shows each signal and places no order) or Live Auto with their broker; which one is their choice. AUTH-REQUIRED for the create and the link.

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": {
      "symbols": "<symbols>"
    },
    "name": "tt_create_signal_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
hybridNoLink the webhook in HYBRID mode (default, required for this template: its sizing, stops and caps are its own logic).
capitalNo
dry_runNoBuild and validate only; create nothing.
symbolsYesThe basket. Plain symbols with `exchange`, or EXCHANGE:SYMBOL each (e.g. ['NSE:RELIANCE','NSE:SBIN'], ['NFO:NIFTY 50'] = NIFTY future, ['MCX:CRUDEOIL'], ['DELTAINDIA:BTCUSD'], ['NASDAQ-EQ:AAPL']) for cash, futures and crypto perps. An OPTION item is an object: {"symbol": "NIFTY 50", "option": "CE"|"PE", "strike": 0 (strike steps from ATM SPOT; 2 = ATM+2, -1 = ATM-1), "expiry": "Current Week"|"Next Week"|"Current Month"|"Next Month", "exchange": "NFO"|"BFO" (optional)}. Index options NFO (NIFTY 50, NIFTY BANK, NIFTY FIN SERVICE, NIFTY MID SELECT) and BFO (SENSEX, BANKEX); stock options NFO. Weekly only for NIFTY 50 and SENSEX; stocks are monthly. No MCX options. The same underlying may appear several times (e.g. CE ATM and PE ATM). Cash, futures and options on NSE/NFO/BFO mix freely; one market clock per template.
exchangeNoDefault exchange for symbols written without a prefix: NSE, NFO, BFO, MCX, NASDAQ-EQ, DELTAINDIA, DELTA, COINDCX, COINSWITCH, ZEBPAY.
intradayNo
session_endNoHHMM on the market clock; default per exchange.
long_productNoMIS / NRML / CNC for the Long legs; default per exchange (NSE: CNC).
working_daysNoe.g. ['Mon','Tue','Wed','Thu','Fri']
session_startNoHHMM on the market clock; default per exchange.
short_productNoMIS / NRML for the Short legs; default per exchange (NSE: MIS).
auto_expiry_exitNo
exit_minutes_before_closeNo

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 only say it is a non-idempotent, non-destructive write; the description adds far more: it creates a persistent template, mints an auth_token that is a bearer credential ("anyone holding it can send signals"), requires hybrid mode, does not deploy, and must be confirmed with the user first. The token-handling instruction ("hand it over once and do not repeat the token in later replies") is a behavioral rule no annotation covers, and the api_link.hybrid_applied == false fallback is spelled out.

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 with purpose, then usage triggers, then capabilities, options, return payload, and deployment caveats in a scannable order with zero filler sentences. It is long, and the dense feature enumeration (sizing variants, stop types, expiry-day exit) is the least economical block, though it maps to the returned `capabilities` field the agent must relay to the user.

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 enumerates the return payload field-by-field (template_id, view_url, api_link, auth_token, python_client, signal_links, guide_markdown, variable_reference, capabilities, next_steps), which is exactly what the burden requires. For a 14-parameter, credential-creating tool it also covers the missing pieces an agent would otherwise get wrong: hybrid-mode enforcement, the no-deploy boundary, and the confirmation requirement.

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?

At 64% schema coverage the description still adds meaning the schema does not: option items are resolved relative to ATM SPOT only when a BUY/SELL is accepted, the strike is then pinned for that entry, and short option legs need broker writing margin and Fix-lot sizing. It also flags which template features each parameter controls (max open positions, master target/SL with reset, session window). It does not explain name, capital, or dry_run, but the schema covers dry_run and hybrid directly.

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 concrete compound verb chain ("Build ... create it in the user's account, link its API token in HYBRID mode, and return everything needed to drive it from outside") naming the exact resource ("Signal Bridge"), and explicitly separates it from Tradetron-condition strategies ("rather than Tradetron conditions"). An agent can tell this apart from tt_create_strategy and tt_update_signal_bridge 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 when the user wants to trade from THEIR OWN signals") with four concrete user phrasings ("send BUY/SELL from my python", "signal-driven portfolio", etc.), plus a prerequisite step ("CONFIRM the basket and exchange with the user first") and an ownership boundary ("It does not deploy"). It also states the credential prerequisite ("AUTH-REQUIRED for the create and the link").

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