thinkerwave
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THINKERWAVE_API_KEY | Yes | Your ThinkerWave API key (create one at thinkerwave.ai/app → Settings → API keys) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_runA | Start a ThinkerWave run on a hard, open-ended problem. |
| run_statusB | Status of a run: round, best score so far, and why it stopped once finished. |
| get_answerC | The best answer so far (or the final one), its confidence, and each finding tagged verified / assumption / guess. |
| list_filesC | Files the run produced (charts, tables, notes). |
| read_fileC | Read one produced file: text files as text (up to 200 KB), images as images (up to 1 MB). |
| stop_runB | Stop a run. The best answer so far is kept. |
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 6 tools
Each tool maps to a distinct phase or resource: start/stop control the run lifecycle, status/answer report progress and results, and list/read handle produced artifacts. There is no meaningful overlap, and the descriptions clearly guide when to use each.
Most names follow a verb_noun snake_case pattern (start_run, stop_run, get_answer, list_files, read_file), but run_status breaks the pattern by using a noun phrase without a verb like get_. The casing and style are otherwise consistent and readable.
Six tools is well-scoped for a run-based problem-solving service. Each tool covers a distinct operation, and there are no redundant or filler tools.
The set covers the core lifecycle: start, stop, monitor status, retrieve the answer, and inspect produced files. A minor gap exists around listing existing runs or cleaning up runs/files, but agents can work around this if they retain run IDs.