wherewent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_jobA | Run a Python/SQLAlchemy job under wherewent and return WHY it was slow. |
| explain_runA | Return the enriched analysis from a saved wherewent JSON file. |
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
The two tools have clearly distinct purposes: analyze_job executes a job and returns analysis, while explain_run interprets pre-existing saved output. No overlap or ambiguity exists between them.
Both tool names follow the same verb_noun pattern: analyze_job and explain_run. The naming is consistent and predictable.
With only two tools, the set feels thin for a server, but the scope is narrowly focused on analyzing slow jobs. The count is borderline for a specialized utility, so a score of 3 is appropriate.
The core workflow of running an analysis and explaining saved results is covered. Minor gaps exist (e.g., no tool for listing or comparing runs), but these are workaroundable and not critical for the primary purpose.