inite-diagnostic
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INITE_TOKEN | No | Generic inite token that can also be used for the inite-diagnostic service. Used if INITE_DIAGNOSTIC_TOKEN is not set. | |
| INITE_DIAGNOSTIC_TOKEN | No | Bearer token for the inite-diagnostic service. If set, takes precedence over INITE_TOKEN. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnostic_questionsA | The eight things a process diagnostic has to establish, in the order they are usually asked. Use them to interview the person yourself — one question at a time, in their language, with options that look like their industry rather than a generic list. Then pass what you collected to read_answers. Runs locally, no account needed. |
| read_answersA | Do the arithmetic on a set of collected answers: enquiries per person, the share that become leads, how many channels arrive without one record, and which of the eight are still blank. Every assumption it had to make is printed beside the result. It stops short of saying what to automate — that is the audit, and it needs an account. Runs locally, no account needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
diagnostic_questions is the interview/collection step, while read_answers is the analysis step that consumes the collected data. Their roles are complementary and clearly distinct, with an explicit handoff. No meaningful overlap exists.
Both names are readable snake_case, but read_answers follows a verb_noun pattern while diagnostic_questions is a noun phrase. The inconsistency is minor and does not create confusion.
Two tools is thin for a general-purpose server, but it fits the narrow diagnostic workflow. Each tool has a clear purpose, yet the set feels minimal and borderline rather than fully scoped.
The server covers gathering diagnostic questions and reading the answers, but it explicitly stops before the audit/recommendation step, which is a notable gap for a diagnostic workflow. The handoff is clear, but the missing automation recommendation leaves the process feeling incomplete.