Skip to main content
Glama

面灵AI 面试助手

update_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": "update_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
examIdYes笔试记录 ID,取自 list_exams
goalIdNo用户的岗位 ID;传 null 解除绑定,不传不改

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 largely covered. The description adds genuinely useful context beyond that: the call requires user authorization with the interviews:write scope. It does not say what happens on failure, whether a title change is reversible, or what the response contains.

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?

A single dense sentence with the two mutation modes front-loaded and the authorization requirement correctly relegated to a parenthetical. Nothing is wasted, though the structure could be marginally clearer by flagging that both editable fields are optional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small three-parameter mutation tool with no output schema, the description covers purpose, auth scope and the unbind semantics reasonably well. The notable gaps are the no-op edge case (calling with only examId) and any statement about the result of the update, which an agent would want before invoking a write.

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 67% and the two documented parameters (examId, goalId) already explain the ID source and the null-versus-omitted semantics for goalId. The description reinforces the rebind/unbind intent but adds nothing about the title parameter, and it does not state whether at least one of title or goalId must be supplied to make a meaningful edit.

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 names a specific verb and resource: modifying an exam record's title or rebinding/unbinding its associated goal (岗位). An agent can immediately tell this is a metadata edit rather than an exam-lifecycle action. However, it does not distinguish itself from the sibling update_exam_customization, which plausibly also edits exam attributes.

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 rather than stated: 'modify the title' or 'rebind/unbind the goal' suggests when the tool applies, and the parenthetical gives an authorization prerequisite (scope interviews:write). There is no explicit when-not guidance and no routing to alternatives such as update_exam_customization or update_goal_hot_words.

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