Claude Error Collector
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| record_errorA | Record a correction from the user and save it as a learned rule in CLAUDE.md. Call this whenever the user corrects you. |
| list_errorsC | List all learned rules from the CLAUDE.md 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 completely distinct purposes: list_errors retrieves existing rules, while record_error adds new rules. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun pattern (list_errors, record_error) with clear action-object naming. The style is uniform throughout the set.
With only 2 tools, the server feels thin for error collection and learning. While it covers basic listing and recording, typical error management systems would benefit from additional operations like updating rules, deleting outdated ones, or searching/filtering errors.
The tools provide minimal CRUD coverage: create (record_error) and read (list_errors) are present, but update and delete operations are missing. This creates a dead-end where rules cannot be modified or removed once recorded, limiting practical utility.