Skip to main content
Glama

面灵AI 面试助手

export_interview_markdown

Read-only

把一场面试的完整记录(问答与答题助手的解题)整理成排版规整的 Markdown,回包给出字数、目录、开头一段与全文下载链接。整理需要几十秒。(需要用户授权,范围 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": "export_interview_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes面试 ID,取自 list_interviews

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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond that: it is a slow operation taking tens of seconds, requires user authorization with the interviews:read scope, and returns word count, TOC, an opening excerpt, and a download link. With no output schema, disclosing the return shape is genuinely useful.

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?

Three compact sentences, front-loaded with the core action, then the return contents, then latency and auth. The parenthetical auth/latency notes are a bit tacked-on but 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 single-parameter tool with no output schema, the description covers what matters: return contents, latency expectations, and authorization requirement. The absence of an explicit alternative-tool contrast is a minor gap but the definition is otherwise sufficient to call correctly.

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?

Only one parameter exists, with 100% schema description coverage; the schema already explains that interviewId comes from list_interviews. The description adds no further parameter semantics, so the high schema coverage sets the baseline at 3.

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: organizing a complete interview record (Q&A plus the answering assistant's solutions) into neatly formatted Markdown. This lets an agent tell it apart from sibling tools such as export_exam_markdown by resource type, although it does not explicitly name or contrast with those siblings.

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: export a full interview record, with latency (tens of seconds) and auth scope (interviews:read) noted, which helps set expectations. There is no explicit statement of when to prefer this over alternatives (e.g., export_exam_markdown, get_interview_transcript), leaving that 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