Skip to main content
Glama

AceRound AI Interview Copilot

reply_to_my_feedback

Add a message (optionally with screenshots) to one of the user's feedback threads; support will follow up. Ids come from list_my_feedbacks. (Requires the user's sign-in with scope account:write.)

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": {
      "feedbackId": "<feedbackId>",
      "content": "<content>"
    },
    "name": "reply_to_my_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
feedbackIdYes
screenshotsNoScreenshots, up to 6

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a non-destructive write with no open-world access, so the description's job is to add context; it does so by naming the auth scope required and the real-world consequence that support will follow up. It does not describe whether the message is immediately visible or what happens on rejection (e.g., oversized content).

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?

Two compact sentences that front-load the action and then layer the id source and auth requirement. The trailing parenthetical about sign-in scope is slightly tacked on, but every clause carries information.

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 three-parameter write tool with annotations and no output schema, the definition covers purpose, id provenance, auth requirement, and the downstream support follow-up. Remaining gaps are minor — no mention of failure modes or whether attachments are validated client-side.

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 only 33%, so the description partly compensates: it tells the agent that feedbackId comes from list_my_feedbacks (real value the schema lacks) and that screenshots are optional attachments to the message. The length limits, base64 encoding, and 6-item cap are left entirely to the schema fields that already document them.

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?

Specific verb plus resource: "Add a message ... to one of the user's feedback threads", with the optional screenshot capability named. It is clearly distinct from create-style siblings (submit_feedback) because it targets an existing thread, and it says explicitly where the thread id comes from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the concrete precondition for use — ids must come from list_my_feedbacks — and flags the required account:write sign-in scope. It does not explicitly exclude alternatives such as submit_feedback for new threads, but the existing-thread framing makes that implicit.

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