Skip to main content
Glama

面灵AI 面试助手

submit_feedback

以用户身份向面灵AI 提交一条反馈(故障、建议或其他),可附截图;处理进展与回复用 list_my_feedbacks / get_my_feedback 查看。(需要用户授权,范围 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 = 故障,SUGGESTION = 建议,OTHER = 其他OTHER
titleNo标题;不传取正文前 20 字
messageYes反馈正文
notifyEmailNo有回复时通知的邮箱;不传则只在站内通知
screenshotsNo截图,最多 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 only declare readOnly=false, destructive=false, openWorld=false; the description adds two things annotations cannot convey: it acts on the user's behalf and requires authorization with scope account:write. It does not say whether submissions are editable or deletable afterward, but the auth requirement is the operationally important disclosure.

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?

A single front-loaded sentence carries the purpose, the optional attachment, and the sibling routing, with the auth scope tucked into a short parenthetical. The semicolon-chained clauses are dense but every element earns its place; no filler.

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?

Five parameters with full schema coverage and no output schema, so the description need not explain return values. It covers purpose, permissions, and post-submission tracking, leaving only minor gaps such as size/format limits for screenshots, which the schema already enforces.

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, message, notifyEmail, screenshots) is already documented. The description only echoes that screenshots are optional and lists the feedback categories, adding little syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('提交一条反馈' to 面灵AI) and enumerates the accepted categories (故障/建议/其他) plus the optional screenshot attachment. It also names the read-side siblings, so an agent can distinguish submitting from tracking without opening either 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?

Explicitly routes follow-up questions ('处理进展与回复') to list_my_feedbacks / get_my_feedback, which gives a clear use-vs-alternative split. It stops short of stating when not to submit (e.g. duplicates, in-app self-service) or prerequisites beyond the auth scope.

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