Skip to main content
Glama

Get interview prep

getInterviewPrep
Idempotent

Get the prep page for one of the candidate's interviews: what the interviewer will look for, stories from their own history to tell, their weak spot, a base salary line and questions to ask, plus pageUrl, the page the "Prep for " buttons open. Works the same for a Clera intro and for a job they applied to themselves and track on their board. Leave interview out for their next upcoming interview of either kind. For a tracked job, pass the interview from listApplications (interview.prep.interview, set once a calendar invite reached their Clera apply address). prep is null when nothing is booked. The first call for an interview writes the page with one model call, so it can take a few seconds; later calls return the same page. Sends nothing to anyone.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault
interviewNoOne interview a prep page is written for

Output Schema

NameRequiredDescriptionDefault
prepYes
pageUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the first call writes the page via one model call and can take a few seconds, later calls return the identical page (explaining idempotentHint=true and readOnlyHint=false), prep is null when nothing is booked, and nothing is sent to anyone. It also discloses that inputs and results are recorded for usage tracking and support.

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?

Front-loaded with purpose, then contents, then parameter routing, then latency/idempotency, then side effects — a sensible order. It is dense and delivered as one long block with some redundancy (the intro-vs-applied point is restated twice), but nearly every sentence carries information an agent needs.

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?

For a single optional polymorphic parameter with an output schema present, the description covers sourcing of the value, the omission default, the null-payload case, latency and idempotency, and side-effect scope. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100% and the schema already describes both oneOf variants, but the description adds the crucial operational meaning: which variant corresponds to a Clera intro versus a self-tracked application, and exactly where to obtain the round/invite identifier. The fallback behavior when the parameter is omitted is also clarified.

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+resource (get the prep page for one interview) and enumerates what the page contains (what the interviewer looks for, stories, weak spot, salary line, questions, pageUrl). It also distinguishes the two supported interview sources (Clera intro vs self-tracked job), which no sibling description could be confused with.

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?

Gives explicit invocation guidance: omit the interview parameter to get the next upcoming interview of either kind, and for a tracked job pass interview.prep.interview sourced from listApplications. It doesn't frame when to prefer this over other prep-related siblings, but the parameter-routing rules are concrete and unambiguous.

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