Skip to main content
Glama

面灵AI 面试助手

list_my_interview_experiences

Read-only

列出用户提交过的面经:公司、岗位、轮次、面试月份、审核状态与审核备注,每页最多 30 条。(需要用户授权,范围 interviews: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_interview_experiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: it requires authorization with the interviews:read scope, states a hard cap of 30 records per page, and lists the fields returned. It does not disclose sort order or pagination completion semantics, which is a minor gap.

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?

A single front-loaded sentence names the resource, then the returned fields, then the page cap, with the authorization note in a trailing parenthetical. There is no redundant restatement of the tool name and every clause carries 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?

For a simple read-only list tool with no output schema, the description compensates well by enumerating the returned fields and the page-size cap, plus the auth scope. It is nearly complete; it only omits result ordering and any note about what an empty list means for the agent.

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 conveys types, defaults and min/max constraints. The description partially compensates by stating '每页最多 30 条', which explains the pageSize maximum, but it says nothing about the 'page' parameter's meaning or how pagination advances, leaving one of the two parameters undocumented in prose.

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 enumerates the entity's fields (company, position, round, interview month, review status, review notes), so the agent knows exactly what the payload is. The possessive '用户提交过的' (submitted by the user) implicitly scopes it to the caller's own records, distinguishing it from the broader list_interviews sibling, but it never names that sibling explicitly.

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 implied rather than stated: the tool is for the caller's own submissions, and the auth scope 'interviews:read' is given as a prerequisite. There is no explicit when-to-use versus when-not, and no mention of alternatives such as list_interviews or generate_interview_experience, so the agent must infer the boundary.

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