Skip to main content
Glama

面灵AI 面试助手

reply_to_my_feedback

在用户自己的一条反馈下追加一条消息(可附截图),客服会继续跟进。反馈 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>",
      "content": "<content>"
    },
    "name": "reply_to_my_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
feedbackIdYes
screenshotsNo截图,最多 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?

The annotations only declare that the tool is non-read-only, non-destructive, and closed-world. The description adds two things the annotations do not: the account:write authorization requirement and the consequence that customer service will follow up on the appended message. It does not say what is returned or whether the message is visible immediately, so the gap is small but real.

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 tight clauses plus a parenthetical: action and constraint first, ID source second, authorization last. No filler, and nothing important is buried.

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 3-parameter mutation tool with no output schema, the definition covers purpose, ownership constraint, ID source, authorization scope, and the follow-up consequence. The only omission is any indication of what a successful call returns (for example, a message ID) or how the appended message appears.

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 coverage is only 33%, so the description must carry more of the load. It supplies the provenance of feedbackId (from list_my_feedbacks) and marks screenshots as optional, but content — the core payload parameter — is only implied by '追加一条消息', with no guidance on what belongs in it beyond the schema's 2000-character cap.

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 pairs a specific verb with a specific resource: appending a message under one of the user's own feedback items, with an optional screenshot. The constraint '用户自己的一条' (the user's own) and the pointer to list_my_feedbacks for the ID clearly separate it from submit_feedback and get_my_feedback.

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 condition for use (an existing feedback owned by the user) and tells the agent where to get the feedbackId, which routes the call correctly. It stops short of explicitly contrasting with submit_feedback (new feedback) or stating when not to use this tool, so it is clear 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