Skip to main content
Glama

面灵AI 面试助手

get_exam

Read-only

读取一场笔试记录:概况与每道题一行概览(题面开头、作答字数)。传 question(题号,从 1 开始)时附上该题的完整题面与作答。整场全文用 export_exam_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": "get_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYes笔试记录 ID,取自 list_exams
questionNo题号,从 1 开始

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false. The description adds context that annotations cannot: the user authorization requirement and the interviews:read scope, plus how the return payload changes between overview mode and single-question mode. It does not cover what happens with an out-of-range question number, but the extra context is solid.

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?

Four short clauses, front-loaded with the default return shape, then the parameter's effect, then the alternative tool, then the authorization note. Nothing is repeated from the annotation block and no sentence is wasted.

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 two-parameter read tool with no output schema, the description states what each mode returns, which sibling to use for the full dump, and the authorization scope. Coverage of the overhead of the whole-exam overview and out-of-range question values is missing, which keeps it short of a 5.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the effect of question: it turns a one-line-per-question overview into the full question text plus the answer for that item. The schema alone would only say 'question number, starting from 1', without stating that consequence.

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 gives a specific verb and resource (读取一场笔试记录) and then defines exactly what comes back: an overview plus a one-line summary per question (question text prefix, answer character count). It also names the sibling export_exam_markdown and states the difference between them, so a reader can choose between the tools 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 explicitly routes whole-transcript reading to export_exam_markdown (整场全文用 export_exam_markdown), which is a concrete when-to-use-this-vs-alternative rule. It also states the condition that changes behavior: pass question only when the full question text and answer for that one item are needed.

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