Skip to main content
Glama

AceRound AI Interview Copilot

update_exam_customization

Update the screenshot-answer customization used in exams and interviews (synced; the desktop client picks it up on next launch). Pass only what changes. Current values via get_settings; save a full custom prompt with save_custom_prompt. (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": "update_exam_customization"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeModeNoCode mode: auto / acm (full program with I/O) / core (only the required function)
codeQualityNoCode style: standard / readable / concise / performance
quickPromptsNoQuick prompts shown in the answer overlay (replaces the list, up to 8)
answerLanguageNoExplanation language; auto follows the UI language in exams and the interview language in interviews
customRequirementsNoExtra requirements
programmingLanguageNoProgramming language, e.g. Python, Java, C++; auto follows the problem

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 readOnlyHint=false and destructiveHint=false, so the description adds genuine value on top: it discloses that changes are synced and only land on the desktop client at next launch, and that the call requires a user sign-in with the interviews:write scope. That is real behavioral context (propagation delay, auth prerequisite) rarely found in annotations. It does not address whether omitted fields are left untouched versus reset, 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.

Conciseness5/5

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

Three short sentences, each doing distinct work: what it changes plus sync behavior, the partial-update rule, and the sibling routing plus auth requirement. The core action is front-loaded and there is no redundant restatement of the title or schema.

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 6-parameter, zero-required mutation tool with no output schema, the description covers the action, propagation timing, auth scope, partial-update contract, and both relevant alternative tools. Nothing an agent needs in order to call this correctly is missing, and return values need not be explained since no output schema exists.

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?

Schema description coverage is 100%, so per-parameter meaning is already carried by the schema, including the 'replaces the list, up to 8' note on quickPrompts. The description still adds non-obvious semantics beyond the schema by establishing the patch/partial-update contract ('Pass only what changes'), which tells the agent it need not fetch and resend current values. Baseline 3 is raised to 4 for that addition.

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: 'Update the screenshot-answer customization used in exams and interviews.' That is concrete enough for an agent to know this mutates the answer-overlay settings rather than exam lifecycle state, and it names two siblings (get_settings, save_custom_prompt) that handle adjacent concerns. It falls short of 5 only because 'screenshot-answer customization' is somewhat internal shorthand for what the schema reveals to be code mode/quality/language/prompt settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs partial updates ('Pass only what changes'), routes reads to get_settings ('Current values via get_settings'), and routes full prompt persistence to save_custom_prompt. An agent has both the when-to-use and the when-to-use-something-else paths spelled out, with no inference required.

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