Skip to main content
Glama

Edit Signal Bridge basket

tt_update_signal_bridge
DestructiveIdempotent

Add or remove symbols (stocks, futures, crypto, option rules) in an existing Signal Bridge, and optionally rename it. The template is edited IN PLACE: the template id and the linked API token stay the same, so the user's existing client and signal links keep working.

Settings (exchange, capital, session, exit minutes, working days, intraday, products, expiry-day exit) are kept from the stored template, and every Initialize Variables value the user tuned (master target/SL, caps, per-symbol sizing of symbols that stay) is carried over. New symbols get the defaults.

Refuses with BRIDGE_DEPLOYED while the strategy is deployed, has subscribers or is public: the rebuild replaces every set, so a running deployment would lose track of its open positions. Tell the user to stop and exit the deployment first, then edit — nothing was changed. BRIDGE_NOT_FOUND = not one of the user's Signal Bridges.

CONFIRM the new basket with the user first (dry_run=true shows it). Returns what tt_create_signal_bridge returns (template_id, basket, auth_token, python_client, signal_links, guide_markdown, ...) plus changed.added_symbols / removed_symbols and the kept settings. Tell the user what was added and removed; give python_client unchanged if they want the updated client (it carries their own token: hand it over once and do not repeat it later). AUTH-REQUIRED.

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew name; empty keeps the current one.
dry_runNoShow the new basket and what changes; write nothing.
symbolsYesThe FULL new basket (not just the changes), in the same forms as tt_create_signal_bridge: 'EXCHANGE:SYMBOL' / plain symbols, or option objects {"symbol", "option": "CE"|"PE", "strike", "expiry", "exchange"?}. The `basket` items a create or update returned are accepted as-is.
exchangeNoDefault exchange for symbols written without a prefix. Defaults to the bridge's own exchange.
template_idYesThe Signal Bridge's TEMPLATE id (not a deployment id).

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?

Goes well beyond the annotations: it explains that the template id and linked API token persist so existing client and signal links keep working, that settings and tuned Initialize Variables values are carried over while new symbols get defaults, and that the rebuild replaces every set. It names the failure modes (BRIDGE_DEPLOYED, BRIDGE_NOT_FOUND), states nothing was changed on error, and flags AUTH-REQUIRED — this is the destructive-semantics context the destructiveHint annotation cannot convey.

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 purpose, then behavior, then errors and return handling; each block earns its place. It is long and the python_client handover coaching ('hand it over once and do not repeat it later') drifts into conversational instruction rather than tool semantics.

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?

No output schema exists, and the description compensates by naming the returned fields (template_id, basket, auth_token, python_client, signal_links, guide_markdown) plus changed.added_symbols / removed_symbols and kept settings. For a destructive, auth-gated mutation with five parameters, everything an agent needs to call it and report back is present.

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 is 3; the description adds meaning by clarifying that carried-over settings and per-symbol sizing apply to symbols that stay, while new symbols get defaults, and that dry_run previews the new basket without writing. It does not add much on template_id or exchange beyond the schema, hence not a 5.

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 (add/remove symbols, optionally rename, in an existing Signal Bridge) and distinguishes itself from creation by describing the operation as an IN PLACE edit of an existing template. An agent can tell this apart from tt_create_signal_bridge without opening the 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?

Explicit when-to-use (editing an existing basket) and when-not (refuses with BRIDGE_DEPLOYED while deployed, has subscribers, or is public, with the remedy 'stop and exit the deployment first'). It also mandates confirming the new basket via dry_run=true before writing, and routes fresh creation to tt_create_signal_bridge by reference.

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