Skip to main content
Glama

Open Support Conversation

tt_open_support_conversation
Destructive

Open a support conversation to escalate to a live Tradetron agent.

USE WHEN: a previous tt_ask_tt call returned escalate=True, OR a tt_diagnose_strategy call could not pin a cause — AND the user has confirmed they want to talk to a human agent. Pass the handoff_payload dict from that earlier result through here verbatim; both tools return one.

DO NOT USE proactively. Always confirm with the user first — opening a support conversation pings real Tradetron support staff.

The conversation is seeded with two messages visible to the agent: a private note carrying the escalation reason, the user's Tradetron identity when it could be resolved, and — when retrieval ran — a one-line summary of what the bot looked at; plus the user's original query as a normal user-side message. On the tt_ask_tt escalation paths the bot has not composed an answer by the time it escalates, so that note carries none; the tt_diagnose_strategy path hands over what the diagnosis found. Either way the agent works the case themselves — never tell the user an answer is already waiting with them.

Returns a session_id and nothing else — there is NO link to hand the user. This conversation lives only inside the assistant: pass the session_id to tt_check_support_response (poll for agent replies) and tt_reply_to_agent (relay user follow-ups). Say that plainly rather than implying they can open it somewhere.

session_context (optional): identifiers you are already holding, so the agent does not start cold — any of {deployment_id, strategy_id, template_id, download_url, request_id}. Pass the SID you diagnosed, the tt_export_strategy download_url, and the _meta.request_id of the failing call when there is one. Identifiers only: free-form blobs are dropped, and each value is truncated.

On status="stub" the support bridge is not connected on this server, so NO conversation was opened and nobody will see the message. Tell the user plainly that you could not reach support from here, give them the Tradetron help centre or the in-app chat, and do not imply anyone has been notified or will reply.

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": {
      "handoff_payload": "<handoff_payload>"
    },
    "name": "tt_open_support_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
handoff_payloadYes
session_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that opening a conversation pings real support staff, describes exactly what messages seed the conversation on each escalation path, warns that no answer is waiting, and explains the status="stub" case where nothing is opened and nobody is notified. That side-effect detail is exactly what the destructiveHint/openWorldHint annotations 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?

Strongly front-loaded with USE WHEN / DO NOT USE headers and no filler sentences; every paragraph adds a distinct fact. It runs long for a two-parameter tool, and the escalation-seeding paragraph could be tightened, which keeps it off a 5.

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 still states the return value precisely (session_id and nothing else, no link to hand the user) and names the follow-up tools. The stub path and the user-facing messaging constraints close the remaining gaps an agent would hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: handoff_payload is described as an opaque dict to pass verbatim from the earlier tool result, and session_context is enumerated with its accepted keys, the rule that free-form blobs are dropped, and the truncation behavior. This is meaning the schema's `additionalProperties: true` objects do not provide.

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: "Open a support conversation to escalate to a live Tradetron agent." It also implicitly separates itself from tt_ask_tt and tt_diagnose_strategy by naming them as the upstream sources of the handoff payload.

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 trigger conditions (`escalate=True` from tt_ask_tt, or an unresolved tt_diagnose_strategy), an explicit precondition (user confirmation), and an explicit exclusion ("DO NOT USE proactively"). The downstream alternatives tt_check_support_response and tt_reply_to_agent are also named with their roles.

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