Skip to main content
Glama

Link Strategy to API Webhook

tt_link_strategy_api
DestructiveIdempotent

Link the Tradetron API webhook token to one of the user's own templates (idempotent — an existing token is reused, never rotated) and set Hybrid / signal-only mode. Returns the user's own webhook auth_token — a credential: anyone holding it can send signals to every deployment of this template — plus the webhook URL, the runtime variables the template's conditions read (and the value its Entry waits for), a copy-and-run python client that carries the token, and a curl example that reads it from $TT_SIGNAL_TOKEN.

Use for "connect my strategy to TradingView / my code / an API", "give me the webhook link", "make it hybrid". For a NEW basket strategy driven by BUY/SELL signals, use tt_create_signal_bridge instead.

Give the user the token and python_client unchanged, once, in this conversation only; do not repeat the token in later replies or summaries. If api_link.hybrid_applied is false, give the user the manual Hybrid steps in api_link.mode_note. 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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "tt_link_strategy_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
hybridNoTrue (default) = Hybrid: the strategy keeps running its own conditions, exits and python AND reads the webhook's variables. False = signal-only (api_controlled=1): Tradetron skips the strategy's own logic — almost never what a condition-builder strategy wants.
strategy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, but the description adds the concrete meaning: an existing token is reused and never rotated, and the returned auth_token is a credential that grants signal-sending power over every deployment of the template. It also discloses the failure path (api_link.hybrid_applied false → use api_link.mode_note) and the AUTH-REQUIRED prerequisite. No conflict with the annotations.

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 the action, then usage triggers, then safety instructions — a sensible order. It is long, but nearly every clause carries operational content (idempotency, credential handling, hybrid_applied fallback). The 'give the token once, never repeat it' handling instruction is arguably housekeeping placed inside a tool definition, costing a little tightness.

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?

There is no output schema, and the description compensates fully by enumerating the returned fields and their sensitivity, plus the branch to take when hybrid_applied is false. For a mutation tool that mints a credential, the agent has everything needed to call it and to report results safely.

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?

Schema coverage is 50%; the hybrid parameter is already fully documented in the schema, so the description's value is mostly in framing the security-sensitive consequence of the returned token. The required strategy_id has no schema description and the description only implies it must be one of the user's own templates — it does not clarify whether that is a template id vs. a deployed strategy id, leaving a real gap for the one required parameter.

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: link the API webhook token to one of the user's own templates, and set Hybrid vs signal-only mode. It also enumerates the returned artifacts (auth_token, webhook URL, runtime variables, python client, curl example), so the agent knows exactly what the action produces. It names the sibling it is not (tt_create_signal_bridge for a NEW basket strategy), making sibling selection unambiguous.

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 explicit triggering utterances ('connect my strategy to TradingView / my code / an API', 'give me the webhook link', 'make it hybrid') and an explicit exclusion routing to tt_create_signal_bridge when the user wants a NEW signal-driven basket. The hybrid boolean's when-not (signal-only 'almost never what a condition-builder strategy wants') is also flagged.

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