Skip to main content
Glama

prepare_for_interview

Read-only

Assembles everything needed to prepare for an interview on a saved GigHQ job application: the job and company context, the candidate's full profile, their Career Journal grouped by role (for STAR/CAR story material), which evidence best matches the role (to emphasize) and which competencies are weakly covered (to address or reframe), and a company briefing (Community Signal, H1B status, size). This read-only tool supplies context only — it does not generate interview questions, write STAR/CAR answers, or assess the candidate.

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": {
      "application_uuid": "<application_uuid>",
      "context": "<context>"
    },
    "name": "prepare_for_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
application_uuidYesUUID of the saved GigHQ job application to prepare for.

Output Schema

NameRequiredDescriptionDefault
purposeYes
candidateYes
fit_signalYes
provenanceYes
applicationYes
career_journalYes
company_contextNo
missing_contextYes
fallback_guidanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "application_uuid"
      -]New value: +[
      +  "application_uuid",
      +  "context"
      +]
  2. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / application_uuid / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / required
      Previous value: -[
      -  "purpose",
      -  "missing_context"
      -]New value: +[
      +  "purpose",
      +  "application",
      +  "candidate",
      +  "career_journal",
      +  "fit_signal",
      +  "missing_context",
      +  "provenance"
      +]
  3. First observed

TDQS

A3.9/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 elsewhere; the description's 'read-only tool supplies context only' largely restates that. It does add genuine behavioral value by disclosing what payload comes back and the boundary that it performs no generation or assessment, but says nothing about error behavior for an invalid or missing application_uuid.

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 dense paragraph that is front-loaded with the core verb and resource, then the contents, then the limits. It has no filler sentences, though the long enumerated middle clause is heavy enough that a reader must parse carefully to extract the exclusions at the end.

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?

With an output schema present the description need not describe return values, yet it still summarizes the payload and clearly limits scope. Combined with annotations covering the read-only profile, the definition is nearly self-sufficient; only failure/empty-state behavior is unaddressed.

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%, so every parameter, including the analytics fields (context, llm_model, conversation_id) and the application_uuid UUID format, is already documented in the schema. The description adds no parameter-level meaning beyond implying the target is a saved application; baseline 3 applies when the schema carries the load.

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 uses a specific verb ('Assembles') plus a precise resource (interview-prep context for a saved GigHQ job application) and then enumerates the constituent parts: job/company context, candidate profile, Career Journal grouped by role, matched evidence, weak competencies, and company briefing. That enumeration lets an agent distinguish it from narrower siblings such as get_job_fit_evidence, get_career_journal_prompts, or get_job_application without opening any schema.

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?

It states the triggering condition clearly (preparing for an interview on a saved application) and adds explicit when-NOT guidance by ruling out generating interview questions, writing STAR/CAR answers, and assessing the candidate. It stops short of naming which sibling an agent should call to perform those excluded tasks, leaving that routing to inference.

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.