Skip to main content
Glama

AceRound AI Interview Copilot

get_my_feedback

Read-only

Read the full thread of one feedback item (every message between the user and support); this marks its replies as read. Ids come from list_my_feedbacks. (Requires the user's sign-in with scope account:read.)

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

Input Schema

NameRequiredDescriptionDefault
feedbackIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior1/5

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

The description states 'this marks its replies as read' — a state mutation — while annotations declare readOnlyHint=true, meaning the tool does not modify its environment. An agent trusting the annotation would treat this as side-effect free; the two signals conflict. The disclosure itself is valuable, but per criteria a contradiction caps this dimension at 1 and is flagged.

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 compact sentences; the core action is front-loaded, the side effect follows immediately, and the id source and auth scope are appended in parentheticals. No padding or redundancy.

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 one-parameter read tool with no output schema, it covers what is returned (the full thread), the side effect, the id source, and the auth scope. Minor gaps remain — pagination of long threads, ordering, and behavior for an invalid or inaccessible id.

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?

With 0% schema description coverage, the single feedbackId parameter is undocumented in the schema, and the description only adds its provenance ('Ids come from list_my_feedbacks'). It does not state format constraints, whether ids expire, or what happens with ids for other users' feedback, so it only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource with explicit scope: 'Read the full thread of one feedback item (every message between the user and support).' This clearly separates it from list_my_feedbacks (which it names as the source of ids) and from reply_to_my_feedback, though it never explicitly says 'use X instead of Y'.

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 supplies a concrete workflow prerequisite ('Ids come from list_my_feedbacks') and an auth prerequisite (sign-in with scope account:read), which is exactly the context an agent needs before calling. It stops short of stating when not to use it (e.g., to reply in the thread, use reply_to_my_feedback).

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