Skip to main content
Glama

AceRound AI Interview Copilot

end_live_interview

Destructive

End the user's live or mock interview in progress, same as "End interview" on the page: settles the session's minutes (live interviews refund time billed after the last exchange) and starts the report. The page closes itself within seconds. This cannot be undone. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (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": "end_live_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoINTERVIEW = live interview, MOCK_INTERVIEW = mock interviewINTERVIEW

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses that minutes are settled with a refund of time billed after the last exchange, that a report is started, that the page closes within seconds, that the action is irreversible, that it may create a payment, and that it requires the interviews:write scope. This is exactly the behavioral context an agent needs before a destructive call.

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?

Front-loads the action and its consequence, then adds cost and auth caveats. Dense but every clause carries information; the parenthetical refund detail and scope note are slightly tucked away but not wasteful.

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?

With no output schema, the description compensates by explaining what happens after the call (report starts, page closes). The only minor gap is that it does not say what the agent should do if the call fails or if no session is active.

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 100% and the single enum parameter is already documented in the schema, so the description only echoes the live-vs-mock distinction. Baseline 3 applies since the schema carries the parameter meaning.

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 ("End the user's live or mock interview in progress") and anchors it to a known UI action ("same as 'End interview' on the page"), so the agent can distinguish it from siblings like interrupt_live_interview_answer or end_exam.

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 condition for use (an interview currently in progress) and a prerequisite workflow (tell the user the cost and get agreement first). It does not explicitly contrast with alternatives such as interrupting or abandoning a session, so it stops short of full when/when-not guidance.

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