Skip to main content
Glama

面灵AI 面试助手

end_exam

把一场进行中的笔试记录标记为已结束,并自动生成标题。只改记录状态,不会关闭用户电脑上的笔试窗口。笔试的发起与截屏答题只能在桌面客户端进行。(需要用户授权,范围 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": {
      "examId": "<examId>"
    },
    "name": "end_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYes笔试记录 ID,取自 list_exams

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=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the mutation is limited to record status, the client-side window is left untouched, and the call requires user authorization with scope interviews:write.

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?

Front-loaded with the action, followed by boundary clarifications and the auth note; each sentence carries information. The desktop-client restriction is slightly tangential to this specific tool but useful for avoiding misuse.

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 mutation with annotations present and no output schema, the definition covers scope, side effects, authorization scope, and even the auto-generated title result. Nothing essential for a correct invocation appears to be missing.

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% and the single examId parameter already documents its source ('取自 list_exams'), so the schema does the heavy lifting. The description adds no syntax or formatting detail beyond that, which is the correct baseline for a fully documented single parameter.

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?

States a specific verb and resource — marking an in-progress written-exam record as ended — and adds a concrete side benefit (auto-generates the title). It implicitly distinguishes itself from the live-interview and window-closing operations, though it never names a sibling tool such as end_live_interview.

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?

The precondition (the record must be in progress) and the platform restriction (exam start/screenshot answering is desktop-client only) are stated, and it clarifies the tool will not close the user's exam window. However, there is no explicit when-to-use versus when-not guidance naming alternatives for closing or deleting an exam.

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