Skip to main content
Glama

面灵AI 面试助手

get_interview_report

Read-only

读取某场面试的复盘报告:总结、各维度得分、优点与不足、建议,以及逐题的问答、得分、评价与改进建议。面试 ID 取自 list_interviews。(需要用户授权,范围 interviews:read)

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": "get_interview_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new operational context not present in the annotations: it requires user authorization with the interviews:read scope. It omits what happens when a report does not exist or is still generating, which is the main remaining behavioral unknown.

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?

The definition is front-loaded with the resource and its contents, then the ID source, then the auth requirement, so the most important facts come first. The long field enumeration is dense but each item describes real returned data rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the burden of describing return values, and it does so thoroughly across both report levels (overall and per-question). Combined with annotations covering safety and the description covering auth scope and ID provenance, an agent has what it needs to invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole parameter interviewId has no schema-level description, only length constraints, so the description must compensate. It does so by stating the value's provenance (取 from list_interviews), which tells the agent how to obtain a valid ID, though it adds no format or example detail beyond that.

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 opens with a specific verb+object pair (读取某场面试的复盘报告) and then enumerates the payload: summary, dimension scores, strengths/weaknesses, suggestions, plus per-question Q&A, score, comment, and improvement advice. That enumeration also implicitly separates it from sibling read tools like get_interview_transcript, so an agent can tell which read tool returns what.

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 gives a concrete prerequisite: the interviewId comes from list_interviews, which is the key routing instruction for a single-resource getter. It does not name a when-not case or point to retry_interview_report for reports that have not been generated yet, so it stops short of full alternative routing.

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