Skip to main content
Glama

AceRound AI Interview Copilot

end_exam

Mark an in-progress assessment record as ended and give it a title automatically. This only changes the record; it does not close the assessment window on the user's computer. Assessments can only be started and solved in the desktop app. (Requires the user's sign-in with scope 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": {
      "examId": "<examId>"
    },
    "name": "end_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYesAssessment id from list_exams

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-destructive, non-read-only, closed-world mutation. The description adds real value beyond that: the side effect of auto-assigning a title, the important limitation that the desktop window is unaffected, and the required auth scope (interviews:write). No return format is described, but the state change itself is well disclosed.

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?

Three short sentences, front-loaded with the core action before the caveats. Each sentence carries information (effect, limitation, auth requirement), though the desktop-app sentence is slightly tangential to invocation.

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 single-parameter mutation with no output schema, the description covers the action, its side effect, its limits, and the auth scope. An agent has enough to call it correctly; only the response shape is unstated, which is minor given no output schema exists.

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?

Only one parameter and the schema already documents it fully (coverage 100%, including 'Assessment id from list_exams'). The description adds no additional meaning about examId, so the baseline of 3 applies.

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: 'Mark an in-progress assessment record as ended,' plus the automatic title assignment. It is clear what the tool does, though it doesn't explicitly contrast itself with siblings like delete_exam or end_live_interview.

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 clear context for when the tool applies ('in-progress assessment record') and an explicit when-not ('it does not close the assessment window on the user's computer'), plus the constraint that assessments can only be started and solved in the desktop app. It stops short of naming an alternative tool for other end-of-assessment needs.

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