Skip to main content
Glama

prepare_mock_interview

Read-onlyIdempotent

Prepare to start a mock interview on the EngMock website: for a catalog ID (or one of your private scenarios) it returns the setup page link, title, type and difficulty, the durations and levels the setup page offers, what the interview costs, a short checklist and the setup steps. With account:read it also says whether the user can start now; otherwise that is "unknown". Read-only: it never starts an interview, reserves or spends credits, or chooses settings. Any valid token can use it.

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

Input Schema

NameRequiredDescriptionDefault
idNoCatalog ID from search_mock_interviews, for example url-shortener. Give this or scenarioId, not both.
scenarioIdNoOr the UUID of one of your own private scenarios. Needs private_scenarios:read (link, title and type) or private_scenarios:practice (link only).

Output Schema

NameRequiredDescriptionDefault
idYes
noteYes
titleNo
sourceYes
paymentYes
guideUrlYes
setupUrlYes
checklistYes
durationsYes
difficultyNo
setupStepsYes
canStartNowYes
questionUrlNo
defaultLevelYes
targetLevelsYes
interviewTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/destructive/idempotent annotations: it discloses that no credits are reserved or spent, that settings are never chosen, that no interview is started, and that any valid token may call it. It also documents graceful degradation — can-start is reported only with account:read, otherwise "unknown" — which is exactly the kind of behavioral nuance an agent cannot infer from structured fields.

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?

Purpose and return contents are front-loaded, and the read-only boundary plus permission notes follow logically. It is dense — the opening clause runs long with nested parenthetical and appositive — but no sentence is redundant.

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?

Despite an output schema carrying the return shape and annotations carrying the safety profile, the description still covers everything an agent needs: the auth requirement, the conditional can-start value, the absence of side effects on credits, and the fact that settings are not chosen. There is no ambiguity about what happens before or during the call.

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 description coverage is 100%, so the either/or between id and scenarioId and the per-parameter permission requirements are already fully documented. The description only restates the alternative ("for a catalog ID (or one of your private scenarios)") and does not add format, precedence, or error semantics beyond the schema, so baseline 3 applies.

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 ("Prepare to start a mock interview") and enumerates exactly what comes back: setup page link, title, type, difficulty, durations, levels, cost, checklist and setup steps. It also carves out a clear boundary ("it never starts an interview"), which separates it from any execution-oriented sibling without needing to name one.

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?

The usage context is clear: call it to get the setup page before starting a mock interview, and it explicitly excludes starting, reserving credits, or choosing settings. Routing to the alternative is implied rather than stated in the description itself — the schema notes the catalog ID comes from search_mock_interviews, and the scenarioId path is documented — but the description does not spell out "search first, then prepare, then start."

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