Skip to main content
Glama

AceRound AI Interview Copilot

interrupt_live_interview_answer

Stop the answer the AI is currently writing in the live interview (what is already written stays). Only works while an answer is being written. Requires the user to have this session open in the browser or desktop app and connected; the page carries it out exactly as if the user clicked the matching button. (Requires the user's sign-in with scope 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": "interrupt_live_interview_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Adds real context beyond the annotations: partial output is preserved, the action is executed client-side by the page as if the user clicked a button, and it requires the interviews:write scope. That said, 'destructiveHint: false' plus the explicit 'what is already written stays' already carry most of the safety profile, and no failure mode (e.g., what is returned when no answer is in progress) is described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and its partial-effect semantics, then preconditions, then auth. No sentence is redundant and nothing is buried.

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 zero-parameter, non-destructive control action with annotations and no output schema, the description covers effect, precondition, client dependency, and auth scope. The only gap is the not-currently-writing case, which is only implied by 'Only works while...'.

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 zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies the target is resolved implicitly from the active live session rather than passed in.

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?

Names a specific verb (stop) and resource (the answer the AI is currently writing in the live interview), and the parenthetical '(what is already written stays)' pins down the exact effect. The 'stop' framing plus the 'Only works while an answer is being written' clause cleanly separates it from the sibling that starts an answer (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 an explicit precondition and an implicit when-not: it only works while an answer is in flight, so an agent knows not to call it before answering starts or after it finishes. It also states the client-side prerequisite (session open in browser/desktop app and connected), though it never names a sibling alternative for the 'nothing is being written' case.

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