Skip to main content
Glama

Send Feedback To Tradetron

tt_send_feedback

Send Tradetron a bug report, a note about a confusing answer, or a feature request, from the AI client. Use it only when the user asks to report something or to request a feature; show them what you will send first.

Attach the _meta.request_id of each call the report is about (every tool response carries one) and the tool names: that is what lets Tradetron reproduce it. Returns a ticket_id (FB-) and status "new" — give the user the ticket id. Each report reaches Tradetron's support team in the same review queue as the in-app assistant's feedback. Replies and status tracking inside the AI client are not available yet (not_yet_available says so); for a conversation with a person now, use tt_open_support_conversation when the user asks for one.

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": {
      "kind": "<kind>",
      "description": "<description>"
    },
    "name": "tt_send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesOne of: bug, confusing_answer, feature_request, other.
tool_namesNoComma-separated names of the tools involved.
descriptionYesWhat happened or what the user would like, in the user's words (up to 4,000 characters).
request_idsNoComma-separated `_meta.request_id` values of the tool calls the report is about, so Tradetron can open their traces.
strategy_idNoThe template id or deployment id the report is about, if any.

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?

Beyond the annotations (readOnly=false, destructive=false, non-idempotent), the description discloses a confirmation requirement, what must be attached to make the report reproducible, the return values (ticket_id as FB-<n>, status "new"), the destination (Tradetron support review queue shared with in-app feedback), and the current lack of reply/status tracking. That is substantial behavioral context an agent could not infer from structured fields.

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?

The purpose and the use-only-when constraint are front-loaded, and most sentences carry a distinct fact (attachments, ticket id, queue, missing reply channel, alternative tool). It is on the long side for a feedback tool and the `not_yet_available` parenthetical is slightly inside-baseball, but nothing is filler.

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 stating exactly what comes back (ticket_id, status "new") and what the agent should do with it. For a non-destructive write tool with full schema coverage, an agent has everything needed to call it 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 coverage is 100%, so the baseline is 3; the description still adds meaning by explaining why request_ids and tool_names matter ("that is what lets Tradetron reproduce it") and where request ids come from (`_meta.request_id` on every tool response). It does not further clarify kind values or strategy_id, but the schema already handles those.

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?

The first sentence names the exact action (send a bug report / confusing-answer note / feature request to Tradetron) and its channel (from the AI client). It also implicitly separates itself from the sibling conversational path by naming tt_open_support_conversation later.

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 gating is given: "Use it only when the user asks to report something or to request a feature; show them what you will send first." The alternative is named with its own trigger condition ("use tt_open_support_conversation when the user asks for one"), so the agent knows both when to use and when not to.

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