Skip to main content
Glama

面灵AI 面试助手

list_interviews

Read-only

列出用户的面试记录(实时面试与模拟面试),每行一场,新的在前,每页 20 场。(需要用户授权,范围 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_interviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNoINTERVIEW = 实时面试,MOCK_INTERVIEW = 模拟面试;不传 = 全部

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?

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's added details about the required auth scope (interviews:read), the newest-first ordering, the one-record-per-line return format, and the page size of 20 are genuinely extra context. It does not state how pagination terminates or what happens on an out-of-range page, which keeps it from a 5.

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?

It is a single tight sentence: resource first, then ordering and page size, with the authorization requirement in parentheses. Every clause carries information, and nothing is padded or repeated, though it could be split to make the auth prerequisite more prominent.

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?

There is no output schema, so the description usefully covers the return shape (one record per line, newest first, 20 per page) and the auth prerequisite. For a two-parameter read-only list tool, this leaves only minor gaps, like total-count behavior or end-of-pagination signaling.

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 50%: the 'type' enum is documented in the schema, the 'page' parameter is not. The description adds '每页 20 场' (page size) and the newest-first ordering, which helps interpret 'page', but it never explains the page bounds (1–100) or what an empty page means. That is a partial compensation, not a full one, so 3 is appropriate.

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 ('列出用户的面试记录') and scopes it to both live and mock interviews. It clearly says what is listed, but it never distinguishes the tool from close-sounding siblings such as list_my_interview_experiences or list_interview_targets, so an agent must infer the boundary itself.

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: 'an agent wanting a user's interview records' follows from the purpose, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The authorization note ('需要用户授权,范围 interviews:read') is a prerequisite, not selection 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