Skip to main content
Glama

get_interview_prep

Generates likely interview questions and preparation tips from a job description, tailored to behavioral, technical, or mixed interviews.

Instructions

Generate likely interview questions and tips for a specific job description

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": {
      "jobDescription": "<jobDescription>"
    },
    "name": "get_interview_prep"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewTypeNomixed
jobDescriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says what content is produced (questions and tips) but not how many items, whether the output is a formatted list versus prose, whether it is generated live or templated, or what happens with a very short or non-job text input.

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 no filler or redundancy. It is efficient, though the brevity contributes to the gaps in the other dimensions rather than indicating a well-scoped tool.

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

Completeness2/5

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

For a generation tool with no annotations, no output schema, and two parameters documented at 0% in the schema, the description should explain the output shape and the interviewType option. Neither is present, so an agent must guess at both before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it only covers jobDescription implicitly. The interviewType parameter and its enum values (behavioral, technical, mixed) are never mentioned, so an agent gets no explanation of how that choice changes the output.

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?

The description names a specific verb and output ('Generate likely interview questions and tips') plus the scope ('for a specific job description'), so it is clearly distinct from prompt-fetching or resume tools in the sibling set. It stops short of explicitly naming an alternative, which keeps it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives such as analyze_job_match or get_cover_letter_prompt, and no exclusions or prerequisites beyond the implicit 'you need a job description'. The only usable signal is the required jobDescription parameter, which the schema already declares.

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