Skip to main content
Glama

面灵AI 面试助手

answer_mock_interview

在进行中的模拟面试里提交用户对当前问题的作答(文字),与面试页上编辑后点击「发送」相同;提交后 AI 面试官给出下一题或结束面试。AI 面试官正在提问时不能提交。需要用户已在网页或桌面客户端打开这场面试的页面并处于连接状态;操作由该页面执行,与用户点击对应按钮完全相同。(需要用户授权,范围 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": {
      "answer": "<answer>"
    },
    "name": "answer_mock_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYes作答原文

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the safety flags (readOnly=false, destructive=false, openWorld=false); the description adds substantial context: the write is proxied through the user's open, connected interview page rather than executed server-side, the resulting side effect is the next question or interview termination, and the required OAuth scope is interviews:write. It also discloses the precondition that makes the call fail (AI currently speaking), which is exactly the non-annotation behavior an agent needs.

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?

Purpose and effect are front-loaded in the first clause, and constraints follow in a logical order. There is mild redundancy: the equivalence to the user clicking 'Send' on the page is asserted twice ('与面试页上编辑后点击「发送」相同' and '与用户点击对应按钮完全相同'), which one sentence would have covered.

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 action tool with no output schema, the definition covers purpose, blocking condition, execution environment, state requirement, side effect, and authorization scope. Nothing an agent needs in order to decide whether to invoke it or to anticipate failure is 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?

Only one parameter (answer), and schema_description_coverage is 100% with a min/max length already declared in the schema. The description's '作答原文' (raw answer text) does not add format, syntax, or content constraints beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb plus resource: submit the user's text answer to the current question of an in-progress mock interview. It explicitly scopes to 'mock interview' (模拟面试), which separates it from live-interview and exam siblings such as answer_live_interview_now and answer_exam_now, and states the downstream effect (AI asks the next question or ends the session).

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?

Gives a concrete exclusion ('cannot submit while the AI interviewer is asking') and a precondition (the interview page must be open in web/desktop client and connected). It does not explicitly name a sibling alternative for the live-interview or exam cases, so the routing is implied rather than stated.

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