workpapers-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKPAPERS_DATA_DIR | No | Set this to point at your own data folder to read the workpapers pack from somewhere else. Defaults to ~/aiProjects/aminWork/automation-portfolio/itgc-audit-workpapers. |
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 |
|---|---|
| get_workpaperA | Full markdown text of one workpaper, 1 to 5: plan, risk and control matrix, test procedures, findings, management letter. |
| list_findingsB | Findings from workpaper 4 with rating and status. Optional rating filter (High, Medium, Low), case-insensitive. |
| control_lookupA | Trace one control end to end: its risk and control row from the matrix, its test procedure and result, and findings that cite it. Accepts A1 or T-A1 style IDs. |
| open_itemsA | What is not closed yet: findings not remediated, tests without a plain Pass result, and drafting placeholders still in the pack. |
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
Each tool targets a different audit artifact: full workpaper retrieval, findings list, control trace, and open items. list_findings and open_items both surface findings, so slight overlap exists, but descriptions clarify scope.
Names use snake_case consistently, but the verb/noun patterns vary: get_workpaper and list_findings are verb_noun, while control_lookup and open_items are noun phrases. Readable but not a single predictable convention.
Four tools for a focused audit-workpaper query server is reasonable; each tool covers a distinct query type. Slightly lean for the domain but not thin enough to be a mismatch.
Core read-only audit queries are covered: workpaper text, findings, control tracing, and open items. Missing enumeration/search helpers (e.g., list_workpapers, list controls, free-text search) are minor gaps that an agent can work around by parsing retrieved markdown.