Skip to main content
Glama

AceRound AI Interview Copilot

submit_feedback

Submit feedback to AceRound on the user's behalf (a bug, a suggestion, or anything else), optionally with screenshots. Follow replies with list_my_feedbacks / get_my_feedback. (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": {
      "message": "<message>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoBUG = something is broken, SUGGESTION = idea, OTHER = anything elseOTHER
titleNoTitle; defaults to the start of the message
messageYesFeedback text
notifyEmailNoEmail to notify when there is a reply; omit for in-app notices only
screenshotsNoScreenshots, up to 6

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only give the safety profile (write, not destructive, closed-world); the description adds the important operational detail that the user must be signed in with the account:write scope and that submissions happen on the user's behalf. It does not say what comes back on success (no output schema exists) or whether screenshots affect limits beyond the schema's maxItems.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences: purpose and scope first, then follow-up tools and the auth prerequisite in parentheses. No filler, and the most decision-relevant information is front-loaded.

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 five-parameter creation tool with a fully documented schema and no output schema, the description covers purpose, scope, auth requirement, and next steps. The only real gap is what the call returns or how the user confirms success, which matters since no output schema documents it.

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 description coverage is 100%, so every parameter (type enum, title default, message, notifyEmail, screenshots) is already explained in the schema. The description only echoes 'optionally with screenshots' and the three feedback kinds, adding no format or behavior detail beyond structured fields.

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 and resource ('Submit feedback to AceRound on the user's behalf') plus the enumerated scope (bug, suggestion, anything else) and optional screenshots. It also implicitly separates creation from the read/reply siblings by pointing at list_my_feedbacks and get_my_feedback for follow-ups.

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?

States the situation this tool covers (reporting a bug, suggesting an idea, or other feedback) and routes follow-up activity to list_my_feedbacks / get_my_feedback. It does not explicitly say when NOT to use it (e.g., replying to an existing thread via reply_to_my_feedback), but the read-vs-write split is inferable.

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