Skip to main content
Glama

get_mock_interview

Read-onlyIdempotent

Read one built-in mock interview's public details (description, opening question, topics, languages) and practiceUrl, its setup page on the website. Grading rubrics and interviewer prompts are never included. Any valid token can use it.

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": {
      "id": "<id>"
    },
    "name": "get_mock_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCatalog ID returned by search_mock_interviews, for example url-shortener.

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
domainNo
topicsYes
summaryYes
companiesYes
difficultyYes
focusAreasNo
descriptionYes
practiceUrlYes
questionUrlYes
targetLevelsNo
interviewTypeYes
defaultLanguageNo
initialQuestionYes
learningOutcomesNo
freeCreditEligibleYes
supportedLanguagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, and non-destructive, so the bar is lower; the description still adds two genuinely new facts — that grading rubrics and interviewer prompts are never returned, and that "any valid token can use it," i.e. a low authorization bar. It does not discuss rate limits or pagination, but neither is relevant for a single-ID lookup.

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?

Two sentences, front-loaded with the core action and the returned fields. The clause "its setup page on the website" is slightly inserted awkwardly after practiceUrl, but it does earn its place by explaining what practiceUrl means.

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?

For a trivial single-ID read with an output schema, full parameter coverage, and rich annotations, the description covers scope, the data deliberately withheld, and access requirements. Nothing an agent needs to invoke it correctly is missing.

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?

With one parameter at 100% schema coverage, the schema already explains that id is the catalog ID from search_mock_interviews with an example. The description adds nothing further about the identifier format, so this is the baseline case rather than added value.

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 concrete verb and resource ("Read one built-in mock interview's public details") and enumerates exactly what comes back: description, opening question, topics, languages, and practiceUrl. The word "built-in" implicitly separates it from private-scenario siblings such as get_private_scenario, but no sibling is named as an explicit contrast, so it falls 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?

Usage is only implied: the schema note that the id comes from search_mock_interviews suggests the search-then-fetch flow, but the description never says when to call this versus prepare_mock_interview or get_private_scenario. There are no stated exclusions or prerequisites beyond access level.

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