Skip to main content
Glama

面灵AI 面试助手

end_live_interview

Destructive

结束用户进行中的实时面试或模拟面试,与面试页上的「结束面试」相同:结算本场时长(实时面试退回最后一句之后多扣的时长)并开始生成复盘报告。结束后面试页会在几秒内自动关闭。结束后不能恢复。会消耗用户的时长、次数或产生付款,执行前向用户说明扣费内容并取得同意。(需要用户授权,范围 interviews:write)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "end_live_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoINTERVIEW = 实时面试,MOCK_INTERVIEW = 模拟面试INTERVIEW

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations (destructiveHint=true, readOnlyHint=false) by disclosing billing mechanics (live interviews refund time deducted after the last sentence), the report-generation side effect, the page auto-closing within seconds, irreversibility, quota/credit consumption or payment, the consent requirement, and the required OAuth 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 core action and its equivalent UI operation, then side effects, then the consent/authorization caveats. Dense but mostly earnings; the parenthetical refund explanation and the separate auto-close and irreversibility sentences add slight redundancy.

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 one-parameter mutation with no output schema, the description supplies everything an agent needs: what happens on success, billing consequences, consent prerequisite, auth scope, and irreversibility. Nothing material is left to inference.

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 enum values are documented in the schema itself (INTERVIEW = 实时面试, MOCK_INTERVIEW = 模拟面试). The description reinforces that both types are supported but adds no new semantics about defaults or consequences of the type choice beyond what the schema already documents; baseline 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?

States a specific verb and resource: end the user's in-progress live interview or mock interview, and anchors it to the UI action ('same as 「结束面试」 on the interview page'), plus what it causes (settle duration, start report generation). It covers both interview types but never differentiates itself from plausible siblings such as delete_interview or end_exam, so it falls short of a 5.

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?

Clear trigger context: use it on an ongoing session, and it must not be invoked until the agent has explained the charge to the user and obtained consent. Irreversibility ('结束后不能恢复') implicitly rules out using it for anything explorable, but no sibling alternative is named for cases such as interrupting or deleting a session.

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