Placed MCP Server

start_interview_session

Initiate a mock interview tailored to your job role and resume. Receive the first interview question and a session ID to track progress.

Instructions

Start a mock interview session for a specific job role. Returns first question and session ID.

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": {
      "resume_id": "<resume_id>",
      "job_title": "<job_title>"
    },
    "name": "start_interview_session"
  }
}

Input Schema

Name	Required	Description	Default
`resume_id`	Yes	Resume ID to use for interview context
`job_title`	Yes	Job title for the interview
`difficulty`	No	Interview difficulty level	medium
`company`	No	Company name (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0May 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool starts a session and returns the first question and session ID, but doesn't mention side effects, error handling, or resource requirements. Overall, it is clear and honest.

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?

A single, front-loaded sentence that effectively communicates the tool's purpose and output. No unnecessary words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description adequately explains the tool's primary function and return values. However, it omits details about what happens if a session already exists, how to handle errors, and how the session ID should be used with sibling tools.

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 well-documented parameters. The description adds no new semantic information about parameters but hints at the output structure. Baseline score of 3 applies as the schema already does the work.

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?

The description clearly states it starts a mock interview session for a specific job role and returns first question and session ID. This differentiates it from siblings like 'continue_interview_session' (which resumes an existing session) and 'get_interview_questions' (which retrieves all questions).

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?

The description implies usage for starting a mock interview but does not explicitly state when to use it versus alternatives like 'continue_interview_session' or 'get_interview_questions'. No guidance on prerequisites or restrictions is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server