Skip to main content
Glama

面灵AI 面试助手

export_exam_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": {
      "examId": "<examId>"
    },
    "name": "export_exam_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYes笔试记录 ID,取自 list_exams

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?

The annotations already cover the safety profile, but the description adds real behavioral context: it needs user authorization with scope interviews:read, takes tens of seconds to run, and returns a word count, table of contents, opening excerpt, and download link. It says nothing about failures, timeouts, or whether repeated calls are idempotent, so it falls short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the output format and result shape, then latency, then the auth requirement. Nothing is padding.

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 one required parameter, full schema coverage, and no output schema, the description covers everything an agent needs: what is produced, what the response contains, how long it takes, and what authorization is required.

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 100%: the single examId parameter is documented, including where to obtain it (list_exams). The description adds no format or edge-case detail beyond what the schema already states, so this sits at the baseline.

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: it consolidates all questions and answers of one exam record into well-formatted Markdown, with code preserved verbatim. The resource scope (笔试记录 / exam record) is enough to distinguish it from the sibling export_interview_markdown, even though that sibling is never named.

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 should call this tool when it needs a Markdown export of an exam. There is no explicit when-to-use or when-not-to-use guidance, no mention of an alternative for interview data, and no polling or retry advice despite the slow nature of the tool.

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