mcp-metsuke-crunchtools
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METSUKE_DB | No | SQLite database path | ~/.local/share/mcp-metsuke/metsuke.db |
| METSUKE_DB_FILE | No | Path whose contents override METSUKE_DB (container secret-file convention) |
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 |
|---|---|
| list_reports_toolA | List all report definitions in the catalog. Returns each definition with its gather prompt, owner agent, schedule, source config, and last-updated time. |
| get_spec_toolA | Return the gather spec (prompt + source config) for a report definition. This is what the autonomous gatherer calls on callback to learn what to collect for the named report. |
| upsert_definition_toolA | Create or update a report definition. The owner_agent field makes the gatherer identity data, not code, so gathering can be re-homed to another agent without a rebuild. |
| save_output_toolA | Persist a gathered report output. The gatherer writes findings here after sweeping the sources. Each finding in payload should carry its own source URL so the compiler can cite it. |
| get_output_toolA | Read a gathered report output for compiling a report. Returns the most recent output by default, or the latest output gathered on a specific date when gathered_date is given. |
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 5 tools
Each tool targets a distinct resource or action: report definitions versus gathered outputs, and read versus write operations. There is no meaningful overlap between listing definitions, fetching specs, upserting definitions, saving outputs, or reading outputs.
All tool names follow a consistent verb_noun_tool pattern: list_reports, get_spec, upsert_definition, save_output, get_output. The naming convention is uniform and predictable.
Five tools is well-scoped for this server's apparent purpose: managing report definitions and gathering/reading report outputs. Each tool serves a clear role without unnecessary redundancy.
The server covers the core workflow: create/update definitions, inspect them, gather output, and retrieve output. A delete operation for definitions or outputs is absent but not clearly required by the stated purpose.