Skip to main content
Glama

面灵AI 面试助手

generate_interview_experience

由一场实时面试的记录整理出面经(面试官问了哪些问题),保存到该面试记录并返回全文;已有面经时重新生成并覆盖。只支持时长满 5 分钟的实时面试。(需要用户授权,范围 interviews: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": {
      "interviewId": "<interviewId>"
    },
    "name": "generate_interview_experience"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes面试 ID,取自 list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds real behavioral detail beyond that: the minimum 5-minute eligibility gate, the required OAuth scope, and the fact that an existing report is regenerated and overwritten. The overwrite of prior content sits slightly awkwardly against destructiveHint=false, but since the artifact is derived and regenerated it is not a true contradiction. It does not say what error or return shape results when the duration gate fails.

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 sequence with semicolon-separated clauses, front-loading what is produced and saved before the eligibility and authorization caveats. Nothing is wasted, though the parenthetical scope note could be trimmed if the authorization requirement were phrased more compactly.

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 one-parameter mutation with no output schema, the description covers the essentials: what is generated, where it is stored, that the full text is returned, the overwrite behavior, the duration eligibility, and the auth scope. The main remaining gap is failure behavior for too-short or non-live interviews, which matters for correct invocation.

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?

There is only one parameter, interviewId, and the schema already documents it at 100% coverage, including the 'take from list_interviews' provenance hint. The description only implies that the ID refers to a live interview record, adding no format or sourcing detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 distills a live-interview record into an interview-experience report (the questions the interviewer asked), saves it to that interview record, and returns the full text. The overwrite clause ('已有面经时重新生成并覆盖') implicitly separates it from a manual-submission sibling, but no sibling is named, so an agent must infer the boundary with submit_interview_experience.

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 clear preconditions: only live interviews of at least 5 minutes, and it requires user authorization with scope interviews:write. It also clarifies the regeneration case. What it does not do is explicitly say when to prefer this over submit_interview_experience or list_my_interview_experiences, so the alternative routing 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