Skip to main content
Glama

面灵AI 面试助手

update_feedback_notify_email

修改一条反馈有回复时通知的邮箱;传 null 表示不再发邮件、只在站内通知。反馈 ID 取自 list_my_feedbacks。(需要用户授权,范围 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?

Annotations only give readOnlyHint=false and destructiveHint=false, so the description adds real value beyond them: the required authorization scope account:write and the effect of passing null (notifications are turned off; only in-site notifications remain). That clarifies an important state change for a tool marked non-destructive. It doesn't describe the response or error behavior, so 4 is the right level.

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?

The description is two dense, front-loaded clauses: first the action, then the null semantics, then the ID source and auth requirement, with no filler. Every clause adds useful 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?

There are two parameters and no output schema, so the description adequately covers the action, both parameters' semantics, the auth requirement, and the ID lookup path. It doesn't say whether the operation is idempotent or how success is reported, but these are minor omissions for a simple update.

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 0%, but there are only two parameters. The description says where feedbackId comes from and what notifyEmail=null means, which adds meaning beyond the bare anyOf definition. It doesn't cover the maxLength or email-format constraints, which the schema already handles.

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 states a specific verb and resource: modifying the reply-notification email of one feedback. It also scopes the operation with the required auth scope (account:write) and the feedback ID source, so an agent can tell it apart from generic update_* siblings such as update_client_settings.

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 prerequisite for the key input (feedback ID comes from list_my_feedbacks) and the semantic fork for the email value (null = no email, only in-site notification). It doesn't state when not to use it, but for a narrow single-purpose mutation, the guidance is clear enough.

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