assurance-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_coverage_toolA | Check whether every month in a folder span is present. Read-only. Names a folder and optionally a period range such as 'January 2024 to December 2025' or 'last 12 months'. |
| check_staleness_toolA | Check whether a document's figures still match a source file the caller names. Read-only. Does not search for a plausible match — both paths are required. Returns UNCHECKABLE when recorded facts are missing and cannot be read. |
| list_dated_files_toolA | List which reporting periods a folder holds from dated filenames. Read-only. Helps an agent decide what to ask next. |
| check_set_coverage_toolA | Check what a task required against what was actually read, over any two sets of keys. Read-only, and touches no filesystem — the caller holds both lists. Use this when the thing you must account for is not dated files in a folder: documents the question spans against the chunks a retriever returned, files changed in a pull request against files reviewed, table partitions against partitions loaded, required controls against controls with evidence, declared eval cases against cases actually run.
Returns the coverage record: |
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 4 tools
The four tools mostly partition cleanly: staleness checking, dated-file listing, folder-month coverage, and arbitrary set coverage are distinct jobs. The two coverage tools have similar names and check_coverage_tool/list_dated_files_tool both read dated filenames, but the descriptions clarify when each is appropriate.
All tool names follow the same verb_noun_tool convention with lowercase snake_case and a consistent trailing _tool suffix. There is no mixing of camelCase, vauge verbs, or haphazard pattens.
Four tools is well within the well-scoped range and each tool earns its place as a distinct read-only assurance operation. The set feels compact without being thin.
The server covers the main assurance workflows: listing available dated periods, checking month-level folder coverage, checking arbitrary set coverage, and checking staleness against a named source. A minor gap is that there is no discovery tool for finding plausible source files for staleness checks, but the descriptions make clear that the caller is expected to supply both paths.