Skip to main content
Glama

AceRound AI Interview Copilot

set_mock_interview_assist

Turn AI assist (a suggested answer for each question) on or off in the mock interview in progress, same as the switch on the page. 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

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

A4.4/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, closed-world mutation, and the description adds genuinely useful context beyond them: the operation requires an active connected session, mirrors a UI click exactly, and needs sign-in with the interviews:write scope. It does not say what happens if no mock interview is in progress or whether the toggle persists across sessions, which keeps it from a 5.

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-loaded with the action and its scope, followed by the operational preconditions; every clause earns its place. Slightly dense with stacked parentheticals, but no wasted sentences.

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 one-parameter boolean toggle with annotations and no output schema, the description covers purpose, session/auth prerequisites, and UI-equivalence behavior. Nothing further is required for an agent to invoke it correctly.

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 single parameter 'enabled' has 0% schema description coverage, but the description compensates by defining the toggle as switching AI assist (a suggested answer for each question) on or off, which fully disambiguates what true/false means. No additional format or default details are needed for a boolean.

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: toggling AI assist (defined parenthetically as a suggested answer per question) on or off in the mock interview in progress. The 'mock interview' scoping plus 'same as the switch on the page' makes it clearly distinct from live-interview tooling like set_live_interview_options.

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: the user must have this session open in a browser or desktop app and connected, in which case it behaves exactly as if the user clicked the button. It does not explicitly name alternative tools for changing interview settings, so it stops short of full when/when-not routing 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