Skip to main content
Glama

面灵AI 面试助手

retry_interview_report

重新生成一份生成失败的面试报告(get_interview_report 提示生成失败时使用)。生成在后台进行,约需一两分钟,之后用 get_interview_report 查看。(需要用户授权,范围 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": "retry_interview_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes面试 ID,取自 list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations mark this as a non-read-only, non-destructive, closed-world write, and the description adds what they do not say: generation is asynchronous, takes about one to two minutes, and requires the interviews:write scope. The description does not explain idempotency: whether a retry discards an existing report, or what happens if one is already in progress. This is a gap for a write tool, but the disclosure is otherwise strong.

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?

Three short clauses, front-loaded with the action and its trigger condition, then the async timing and next step, then the permission requirement. No sentence is redundant or padded.

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 async write with no output schema, this definition covers the trigger, the latency, the observation path, and the authorization requirement. It is complete enough to call correctly. Only the edge case of repeated or concurrent retries is unaddressed.

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 100%, and the single interviewId parameter is documented in the schema as 'interview ID, taken from list_interviews'. The description adds no semantics about that parameter beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: regeneration of an interview report whose generation failed. It distinguishes itself from get_interview_report by naming that tool as both the trigger condition and the follow-up viewer, so an agent can choose between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit trigger (use when get_interview_report reports a generation failure) and an explicit follow-up (poll get_interview_report after one to two minutes). Formally stating the required authorization scope (interviews:write) adds a concrete prerequisite that is not in the annotations.

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