Skip to main content
Glama

Reply to Support Agent

tt_reply_to_agent
Destructive

Relay a user's follow-up message to the live support agent.

USE WHEN: a tt_open_support_conversation has already happened in this session AND the user wants to send something to the agent (a clarification, a follow-up question, an answer to an agent prompt).

DO NOT USE for the user's original question — that's seeded by tt_open_support_conversation. Only use for messages SENT AFTER the conversation is open.

content is the user's literal text. Don't rewrite or summarize — pass it through. The agent sees it as a normal customer message in the conversation.

TEXT ONLY. This relay carries no attachments, and files the agent sends back are dropped. If the user needs to send a screenshot or a document, tell them to email it to support@tradetron.tech quoting the same issue — do not tell them to attach it here.

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": {
      "session_id": "<session_id>",
      "content": "<content>"
    },
    "name": "tt_reply_to_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With annotations already declaring destructive/write semantics, the description still adds real context: the payload is text-only, agent-sent files are dropped, the forwarded text appears to the agent as a normal customer message, and there is a documented fallback channel (email) for attachments. It stops short of covering failure behavior — what happens if session_id is stale/expired, or whether the call blocks awaiting an agent response — so it is strong but not complete.

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 the one-line purpose, then branches cleanly into USE WHEN / DO NOT USE / parameter rules / text-only constraint. Every section carries information, though the content paragraph restates the pass-through rule twice ('literal text' and 'don't rewrite or summarize').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a side-effecting, two-parameter relay with no output schema, this covers usage preconditions, payload semantics, and the attachment limitation — enough to call it correctly. The remaining omissions (failure modes, whether a response returns inline) are secondary but real for a write-class tool.

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%, so the description must carry the parameter burden and mostly does: `content` is defined as literal, unrewritten user text, and `session_id` is implied to come from the already-open conversation. It gains meaning beyond the bare schema types, though it never names session_id explicitly or says what an invalid one does.

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 concrete verb plus resource — 'Relay a user's follow-up message to the live support agent' — and immediately scopes it against the sibling that seeds the original question (tt_open_support_conversation). An agent can distinguish the two roles without opening either 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 USE WHEN with preconditions (conversation already open in this session, user wants to send a clarification/follow-up/answer) and an explicit DO NOT USE covering the original question case. It names the alternative tool and the exact condition that routes to it.

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