Skip to main content
Glama

面灵AI 面试助手

set_mock_interview_assist

开关进行中的模拟面试的 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": {
      "enabled": "<enabled>"
    },
    "name": "set_mock_interview_assist"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-open-world mutation. The description adds genuinely non-obvious behavior beyond that: the write is dispatched to and performed by the user's open client page, is equivalent to a UI button click, and requires the interviews:write authorization scope. It stops short of saying what happens when the client is disconnected or what the call returns.

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?

The core action is front-loaded in the first clause, followed by the precondition and the authorization note in a logical order. The parenthetical asides are dense but each carries real information; nothing is redundant.

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

Completeness4/5

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

For a one-parameter toggle, the definition covers what it does, the operational precondition, the execution model, and the auth scope. The remaining gap is failure behavior (client not connected or unauthorized), which an agent would want before invoking.

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 0% for the single boolean parameter, so the description must carry the meaning. It explains what the assist does and frames the tool as a switch, from which on/off semantics for 'enabled' are inferable, but it never explicitly states that enabled=true turns the assist on and false turns it off.

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: toggling the AI assist for an in-progress mock interview, with a concrete explanation of what the assist produces (a reference answer per question). The 'mock interview' scope implicitly separates it from the live-interview siblings, though no sibling is named explicitly.

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 clear precondition for use: the user must have this interview open in a web or desktop client and be connected, because the page executes the action. It does not name alternative tools (e.g. option-setting or answering siblings) or say what to do when the precondition fails, but the when-to-use context is unambiguous.

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