Skip to main content
Glama

AceRound AI Interview Copilot

update_feedback_notify_email

Change the email notified when a feedback item gets a reply; pass null to stop emails and keep in-app notices only. 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>",
      "notifyEmail": "<notifyEmail>"
    },
    "name": "update_feedback_notify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackIdYes
notifyEmailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-destructive, closed-world), the description discloses the auth requirement (sign-in with scope account:write) and the side effect of null input (emails stop, in-app notices remain). That is meaningful behavioral context annotations do not carry. It doesn't describe failure behavior for an invalid email or insufficient scope, keeping it below 5.

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 sentences plus a short parenthetical, front-loaded with the primary action and null behavior before the id provenance and auth note. No redundant restatement of the tool name or schema.

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 2-parameter mutation with annotations and no output schema, the definition covers purpose, id source, null semantics, and auth scope — essentially everything needed to call it correctly. Only error/permission-failure behavior is unaddressed, a minor gap.

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 it does add real meaning: notifyEmail=null means stop emails and retain in-app notices, and feedbackId values come from list_my_feedbacks. Format constraints (email format, max length) are left to the schema, which handles them adequately.

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 description gives a specific verb+resource: 'Change the email notified when a feedback item gets a reply', with the exact trigger condition (a reply arrives). This is clearly distinct from siblings like reply_to_my_feedback or list_my_feedbacks, so an agent can pick it without opening a schema.

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 tells the agent the prerequisite data source ('Ids come from list_my_feedbacks') and the semantics of the null case, which is practical when-to-use guidance. It stops short of naming explicit alternatives or when-not-to-use conditions, so it is strong but not exhaustive.

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