Skip to main content
Glama

面灵AI 面试助手

list_my_feedbacks

Read-only

列出用户提交过的反馈(每行一条,最近有回复的在前,每页 20 条),含状态、往来条数、是否有未读回复与最后一条消息摘要。(需要用户授权,范围 account:read)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_feedbacks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description adds real behavioral context: ordering ('最近有回复的在前'), fixed page size of 20, the fields surfaced per row, and the required authorization scope 'account:read'. This is meaningful disclosure that the annotations alone would not supply.

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 dense sentence plus an authorization note, with the key facts (scope, ordering, page size, returned fields) front-loaded. Slightly compressed by the nested parentheticals, but no sentence is wasted.

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?

With no output schema, the description correctly takes on the burden of describing returned fields (status, exchange count, unread flag, last message summary) and notes the auth scope. The only shortfall is the thin coverage of the page parameter.

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 description should carry the load for the single 'page' parameter; it only implies pagination via '每页 20 条' and never explains the page index, its 1-based nature, or the max of 100. It adds partial but not sufficient meaning.

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 states a specific verb and resource ('列出用户提交过的反馈') and scopes it to the user's own submissions, so it is distinguishable from the singular get_my_feedback and from reply_to_my_feedback. It does not explicitly name those siblings, which keeps it just 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the listing semantics and the ordering/paging details; there is no explicit statement of when to pick this over get_my_feedback for a single item's detail. An agent can infer the intent, but the routing decision is left to inference.

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