Skip to main content
Glama

面灵AI 面试助手

ask_live_interview

Destructive

在进行中的实时面试里替用户提一个问题:这段文字作为面试官的问题交给 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": {
      "question": "<question>"
    },
    "name": "ask_live_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes问题原文

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag it as non-read-only and destructive; the description adds a lot beyond that — it interrupts an ongoing answer stream, reuses the desktop 'voice question' pipeline, is executed by the interview page (same effect as the user clicking the button), bills by online duration, consumes quota or incurs payment, and requires the caller to explain charges and get consent first, plus the interviews:write scope. This is substantially more than the structured fields convey.

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 the key side effect lead the description, and the later clauses (pipeline, prerequisites, billing, consent, auth scope) each carry operational information. It is dense and sentence-heavy — the interruption detail could be tightened — but nothing is decorative filler.

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 tool with no output schema, the description covers everything an agent needs: what the text does, where the answer appears, the interruption behavior, connection and already-started prerequisites, and the billing/consent obligation. No significant behavioral gap remains for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents '问题原文', so the baseline is 3. The description adds role semantics — the string is submitted verbatim as the interviewer's question and drives the AI's answer — which clarifies how the argument is consumed, though format/length constraints remain solely in the schema.

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 and resource — submit a question on the user's behalf into an in-progress live interview — and pins down what happens to the text: it becomes the AI interviewer's question and the answer renders on the interview page. The in-line note that an in-flight answer stream is interrupted first cleanly separates it from interrupt_live_interview_answer and answer_live_interview_now.

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 concrete preconditions: the user must have already clicked 'Start interview', and the interview page must be open in web or desktop client and connected, because the page performs the operation. It doesn't explicitly name sibling tools or state when a caller should prefer answer_live_interview_now or interrupt_live_interview_answer instead, so it stops short of full when/when-not routing.

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