Skip to main content
Glama

面灵AI 面试助手

get_my_feedback

Read-only

读取一条反馈的完整往来(用户与客服的每条消息),读取后该反馈的未读标记清除。反馈 ID 取自 list_my_feedbacks。(需要用户授权,范围 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

A3.5/5.0
Behavior2/5

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

The description discloses a real side effect that the structured data hides: reading the thread clears the feedback's unread marker. That is a state mutation, which sits in tension with readOnlyHint=true and destructiveHint=false, so the definition and the annotations cannot both be taken at face value. The disclosure itself is valuable (side effect, auth scope, ID provenance), but the conflict with the declared read-only profile is a serious defect an agent must resolve.

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?

Three compact clauses, front-loaded with the core action, then the side effect, then the ID source and auth scope. Every clause carries information; the only minor inefficiency is that the parenthetical auth note could be folded into the main flow.

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 single-parameter read tool with no output schema, the description covers the action, the side effect, the ID source, and the auth scope, which is most of what is needed to call it correctly. It does not say what the returned message list looks like or whether long threads are paginated, which matters for a 'full conversation' read.

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 0%, so the schema only tells the agent that feedbackId is a 1-64 character string. The description compensates partially by naming list_my_feedbacks as the authoritative source of that ID, which is genuinely useful provenance. It still says nothing about format or what an invalid ID yields, so it does not fully cover the gap.

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: it reads the complete message thread of a single feedback item, explicitly scoped to 'every message between user and support'. That is far more precise than the name alone and distinguishes it from list_my_feedbacks, which it names as the ID source. It does not explicitly position itself against reply_to_my_feedback, so it falls short of a 5.

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 workflow (obtain feedbackId from list_my_feedbacks) and the authorization requirement with the exact scope account:read, which is exactly what an agent needs before attempting a call. It gives no explicit 'do not use this for X' exclusion, so it is clear context rather than full routing guidance.

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