claude-interview-mode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | No | Optional Supabase URL for private database | |
| SUPABASE_ANON_KEY | No | Optional Supabase anon key for private database |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_interviewA | Start a new interview session. Use this when beginning a conversational exploration of a topic, project, or decision. |
| recordA | Record a Q&A exchange or a decision made during the interview. Call this after each meaningful exchange to maintain context. |
| get_contextA | Get the full context of the current interview session. Use this to review what has been discussed so far before asking the next question. |
| end_interviewA | End the current interview session and get a structured summary of all Q&As and decisions. Use this when enough information has been gathered. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| interview | Activate interview mode - Claude will ask questions one at a time to explore a topic conversationally. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: start_interview initiates, record logs exchanges, get_context retrieves current state, end_interview concludes. No overlap or ambiguity.
All tools use imperative verbs, mostly in verb_noun form (start_interview, end_interview, get_context). 'record' is a single verb but fits the pattern; minor inconsistency but still predictable.
Four tools is ideal for an interview mode server. Each tool serves a fundamental operation (start, record, read context, end) without being overly minimal or excessive.
The tool set covers the full interview lifecycle (start, record, review context, end). A potential gap might be editing or removing a record, but the core workflow is complete.