Skip to main content
Glama

面灵AI 面试助手

delete_exam

Destructive

删除一场笔试记录及其全部题目与作答。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 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": "delete_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYes笔试记录 ID,取自 list_exams

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds substantial context beyond that: the deletion is irreversible ('删除后不能恢复'), it cascades to all questions and answers, and it requires authorization in the interviews:write scope. The mandatory user-consent step is behavior an agent could not infer from the annotations alone.

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 with zero filler: action and cascade scope first, irreversibility and consent requirement second, authorization scope last. Every clause carries decision-relevant information and nothing repeats the title or schema.

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?

For a single-parameter destructive tool with no output schema, the description covers everything an agent needs before calling: what is removed (including cascaded children), that it cannot be undone, that consent must be obtained, and which authorization scope applies.

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 is fully documented in the schema, including where to obtain it ('取自 list_exams'). The description adds no further parameter-level meaning, so the baseline of 3 applies.

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 plus resource in '删除一场笔试记录' and even specifies cascade scope ('及其全部题目与作答'), so an agent knows exactly what is removed. It does not explicitly contrast with the similarly named sibling delete_interview, but the distinct resource (exam vs. interview) is unambiguous from the name and text.

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 clear precondition for use: explain to the user what will be deleted and obtain consent before executing, which is genuine operational guidance rather than a restatement. It does not name any alternative tool or a when-not-to-use case, so it falls just short of full routing guidance.

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