Skip to main content
Glama

Start a mock interview

start_mock_interview
Read-only

Starts a practice mock interview for a job: returns 5 realistic interview questions for the given job title (and company, if given), shown as a question card.

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": {
      "role": "<role>"
    },
    "name": "start_mock_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe job title, e.g. "Sales associate" or "Data analyst".
companyNoOptional company name, e.g. "Target".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior detail (exactly 5 questions, tailored by company when supplied, rendered as a question card), but says nothing about whether repeated calls produce different questions despite idempotentHint=false.

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?

A single front-loaded sentence with the verb first and a compact parenthetical qualifier; no filler or redundancy. The nested parenthetical slightly reduces readability but costs almost nothing.

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 simple two-parameter, non-destructive tool with a 100%-covered schema and full annotations, the description supplies the essential missing piece: the return shape (5 questions as a question card). It omits how a session continues after generation, which is a minor but real gap given there is no output schema.

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%, with both parameters documented including examples and length limits, so the baseline is 3. The description only echoes that company is optional and used "if given," adding little beyond the schema.

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 ("Starts a practice mock interview") and immediately says what it returns: 5 realistic interview questions for the given job title/company. This clearly separates it from the feedback sibling, though it never names that sibling explicitly.

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 via the "practice" framing and the requirement of a job role; there is no explicit when-to-use, when-not-to-use, or pointer to what to do after the questions are generated (e.g., answer then call get_answer_feedback).

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