Skip to main content
Glama

Check Support Response

tt_check_support_response
Read-onlyIdempotent

Poll a support conversation for new agent (operator) messages.

USE WHEN: the user has asked whether the agent has replied yet ("any update?", "did they respond?"), or the user is waiting on a support conversation they opened in this chat and sends their next message. Only for a conversation the user opened with tt_open_support_conversation.

session_id comes from a prior tt_open_support_conversation call. since_timestamp_ms is a cursor — pass back the latest_timestamp from the previous poll to skip messages you've already shown the user. On the first poll pass 0.

Returns only operator-side text messages — the user's own echoed messages and the bot's private context note are filtered out. Each message has a content string you can surface to the user, plus a timestamp you should remember as the new since_timestamp_ms for the next call.

status "resolved" (or resolved: true beside new messages) means the team closed the conversation: tell the user, and open a new one if they still need help. assigned_operator names the agent holding it, when one does.

If messages is empty, no new replies. Say "no reply from the agent yet" — and do NOT promise one is coming: this surface has no signal for whether support is online, so never state or imply that someone is about to answer. If the user is waiting on something urgent, give them help.tradetron.tech and +91 80 4718 9100 as well.

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>"
    },
    "name": "tt_check_support_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
since_timestamp_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly=true, idempotent=true, non-destructive), and the description adds substantial context beyond them: operator-message filtering, the resolved/resolved:true state meaning, assigned_operator semantics, and an explicit instruction never to imply support is online. It also supplies an escalation path (help site and phone) for urgent waits, which 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?

Well front-loaded: the one-line purpose precedes the USE WHEN block, then parameter guidance, then return-value semantics, then edge-case handling. Length is justified by the polling/cursor protocol, though the pod-picking-and-escalation paragraph could be tightened slightly without losing meaning.

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 by documenting the returned fields (content, timestamp, status, resolved, assigned_operator) and the empty-messages case. For a two-parameter, read-only polling tool this covers everything an agent needs to call it and interpret results correctly.

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 description coverage is 0%, so the description carries the burden and largely does: it explains session_id provenance (from a prior open call) and defines since_timestamp_ms as a cursor fed by the previous poll's latest_timestamp, with 0 on the first call. It does not state the unit/format explicitly (epoch milliseconds), which is only inferable from the parameter name.

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 ('poll a support conversation for new agent (operator) messages') and immediately scopes it to conversations opened via tt_open_support_conversation, which distinguishes it from the sibling support-check tools. An agent can identify the tool and its scope 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?

An explicit USE WHEN block gives both the triggering condition and verbatim user utterances ('any update?', 'did they respond?'), plus a second condition (user waiting and sends next message). The negative constraint ('only for a conversation the user opened with tt_open_support_conversation') rules out misuse on external tickets.

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