golden-dataset-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_datasetA | Initialise a new version-controlled golden dataset at dataset_path. Creates a .golden_dataset/ directory there. Fails if one already exists at that path — delete .golden_dataset/ manually to start fresh. |
| add_entryA | Add a question-answer pair to the working tree of a golden dataset. Entries added here are NOT yet versioned — call commit_version to snapshot them. dataset_path must already be initialised. |
| update_entryA | Update fields of an existing working-tree entry by its id. Only fields you provide are changed; omitted fields are left as-is. Raises an error if entry_id is not found in the working tree. |
| delete_entryA | Remove an entry from the working tree by its id. Does not affect already-committed versions. |
| list_entriesA | List entries in a dataset. Omit version to see the uncommitted working tree; pass a version (e.g. '1.0') to see a committed snapshot. |
| commit_versionB | Snapshot the current working tree as a new immutable dataset version. Versions auto-increment (1.0 -> 1.1 -> 1.2...). Fails if the working tree is empty. |
| diff_versionsB | Show entries added, removed, or changed between two committed versions. |
| evaluate_answersA | Score actual LLM/RAG-generated answers against the golden dataset using TF-IDF cosine similarity (no LLM call, no API key needed). actual_answers must be supplied in the same order as the entries in
the target version. Omit |
| dataset_statusB | Show the current state of a golden dataset: name, current version, and working tree size. |
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 9 tools
Each tool has a clearly distinct purpose: init, add, delete, update, list, commit, status, diff, and evaluate. No two tools overlap in functionality.
All tool names follow the verb_noun pattern in snake_case, e.g., add_entry, commit_version, list_entries. Consistent and predictable.
9 tools is well-scoped for a version-controlled golden dataset server. It covers all essential operations without being bloated or sparse.
The tool surface covers init, CRUD for working tree, versioning, listing, status, diff, and evaluation. Minor gap: no dedicated get-single-entry tool, but list_entries likely returns full entries.