Skip to main content
Glama

AceRound AI Interview Copilot

get_exam

Read-only

Read one assessment record: summary plus one line per question (start of the question, answer length). Pass question (1-based) to include that question and its answer in full. Use export_exam_markdown for the whole record. (Requires the user's sign-in with scope interviews:read.)

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": "get_exam"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYesAssessment id from list_exams
questionNoQuestion number, starting at 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered; the description adds genuinely new facts: the default response is truncated (question start plus answer length), one question can be expanded in full, and the call requires a user sign-in with the interviews:read scope. The remaining gap is error/empty behavior for an unknown examId or an out-of-range question number.

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 compact sentences with zero redundancy: return shape first, the parameter's effect second, the alternative and auth requirement last. The parenthetical auth note is the only arguably marginal element and is short enough to earn its place.

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 carries the burden of describing returns and does so concretely (summary, per-question line, expanded answer). For a two-parameter read-only tool that is close to complete; only failure modes for a bad examId or question number are unaddressed.

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 already documents examId's provenance (from list_exams) and question's 1-based numbering. The description does add meaning the schema lacks — that `question` returns that question and its answer verbatim rather than truncating — but it does not clarify what omitting `question` yields for very large exams beyond the general summary line format.

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 ("Read one assessment record") and immediately characterizes the returned content: a summary plus one truncated line per question. It also distinguishes itself from the bulk sibling by pointing at export_exam_markdown, so an agent can tell the two reads apart without inspecting either schema.

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 an explicit routing rule: use this tool for a single record, use export_exam_markdown for the whole record, and pass `question` when the full text of one answer is needed. That covers the main decision the agent faces, though it does not state whether the export sibling should be preferred for very long exams or what to do when a question number is out of range.

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