Skip to main content
Glama

AceRound AI Interview Copilot

export_exam_markdown

Read-only

Turn a whole assessment record (every question and answer) into tidy Markdown with code kept as is. Returns its length, outline, opening, and a download link for the full text. Takes a few dozen seconds. (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": "export_exam_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
examIdYesAssessment id from list_exams

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, not destructive, closed-world); the description goes well beyond that by disclosing that the returned payload is NOT the full document but a length, outline, opening, plus a download link, and that the call is slow enough to plan around. Auth scope and latency are exactly the operational context annotations cannot carry.

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, front-loaded with the transformation, then the return shape, then cost and auth. Every clause carries information an agent needs; nothing is repeated from schema or annotations.

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 correctly compensates by explaining what comes back and that the full text arrives via a download link. A brief note on whether the download link expires or what the outline looks like would close the remaining gap.

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, examId, and the schema already documents it fully ("Assessment id from list_exams") at 100% coverage. The description adds no format, constraint, or sourcing detail beyond that, so baseline 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: turns a whole assessment record (questions and answers) into Markdown, preserving code blocks. "Assessment record" implicitly separates it from the interview export sibling, but it never names or contrasts that sibling, so the differentiation is left to inference.

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?

Gives a real precondition (user's sign-in with interviews:read scope) and a cost signal (a few dozen seconds), which effectively implies when it is and isn't viable. It does not say when to pick this over export_interview_markdown or get_exam, and offers no exclusions.

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