Skip to main content
Glama

AceRound AI Interview Copilot

update_exam

Rename an assessment record, or change or clear the role it is linked to. (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": "update_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
examIdYesAssessment id from list_exams
goalIdNoThe user's role (goal) id; null clears the link, omit to keep it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile: this is not read-only and not destructive, and it is closed-world. The description adds the caller's authentication requirement, the interviews:write scope, which the schema and annotations do not state. It does not discuss reversibility or rate limits, but for a small update tool the auth disclosure adds real value.

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?

Two short sentences, with the operation stated first and the prerequisite second. No filler, no repetition of schema detail.

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?

The tool is small (three parameters, no nested objects, no output schema), and its annotations already cover the safety profile. The definition states what changes and what auth is needed, so it is sufficient to call correctly. Only the boundary against the related customization tool is unstated.

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 67%, and that schema already explains that examId comes from list_exams, and that a null goalId clears the link while omitting it preserves it. The description's phrase 'change or clear the role' is consistent with that but largely restates it. It indirectly covers the title parameter through 'Rename', without adding format details.

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?

The description names a concrete verb and resource: rename an assessment record, and change or clear its linked role. That is far more specific than the tool name alone. It does not explicitly contrast the tool with the sibling tool update_exam_customization, so it stops short of a 5.

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

Usage Guidelines3/5

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

It implies usage through the scope requirement and the two supported operations, but it never says when to choose this tool over update_exam_customization, delete_exam, or the other exam siblings. An agent must infer the boundary from the sibling names.

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