Skip to main content
Glama

面灵AI 面试助手

answer_exam_now

在桌面客户端的笔试浮窗上按「直接答」:停止仍在进行的查证,按已有内容立即写出答案(不是中止,本题照常完成)。只在笔试题正在作答时有效。(需要用户授权,范围 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": "answer_exam_now"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description goes well beyond that by disclosing the side effect (pending verification is cancelled and discarded), that the question still counts as completed, and that it needs user authorization with scope interviews:write. That is genuinely useful context for a mutating action. It does not say what happens if verification had already produced a partial answer, or what the tool 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?

One dense sentence plus parentheticals: the triggering surface comes first, then the effect, then the clarification about non-abort, then validity, then the auth scope. Every clause carries information. It is on the edge of over-packed — a parenthetical nested inside a parenthetical — but nothing is redundant.

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 zero-parameter, no-output-schema mutation, the description supplies everything an agent needs: the exact UI context, the behavioral semantics of the action, the precondition, and the authorization scope. There is no return-value gap because no output schema exists and the outcome is described in prose.

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?

The tool takes no parameters, so there is nothing for the description to clarify beyond the schema, and the baseline of 4 applies. The description does not waste words re-documenting an empty input object.

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 action on a specific surface (the desktop client's written-exam floating window, the 「直接答」 button) and states the outcome: stop in-progress verification and immediately produce the answer from existing material. It actively disambiguates from an abort ('不是中止,本题照常完成'), which is the most likely confusion against the interrupt/abandon siblings. It stops short of naming a sibling tool, so it is not a full 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?

It gives a clear precondition for use: '只在笔试题正在作答时有效' (only valid while a written-exam question is being answered), plus an explicit exclusion of the abort reading. What is missing is routing — nothing tells the agent to use the live-interview or mock-interview counterpart when the context is not an exam, so the agent must infer that boundary itself.

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