Proofpane
OfficialServer 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 |
|---|---|
| bashC | Execute a bash command in the project directory. Output is captured and truncated. |
| readB | Read a file from the project directory. Path traversal is blocked. |
| writeB | Write content to a file (overwrites). Parent directories are created. |
| editB | Replace one occurrence of old_string with new_string in a file. |
| globC | Find files matching a glob pattern under the project. |
| grepB | Search for a regex pattern in files (uses system grep -r -n). |
| listdirC | List contents of a directory. |
| search_compliance_docsA | Search the Proofpane governance / compliance document corpus via the cloud RAG service. Returns the top N matching chunks with source + relevance score. Default collection + retrieval method come from this agent's rag_config (configured in the Proofpane UI); override per-call with the |
| ingest_to_ragA | Upload a LOCAL file into the Proofpane governance RAG corpus. The cloud parses it (PDF / DOCX / HTML / text), DLP-scrubs secrets, chunks + embeds it, and audits the ingest. After this, the file's contents are searchable with search_compliance_docs on the returned collection. Use when the user wants a local document made available for governed retrieval / Q&A. |
| session_searchA | Search + recall past Hermes conversations (governed). Discovery: pass |
| skills_listA | List available Hermes skills (name + description + category), governed. Optional |
| skill_viewB | Read a skill's full SKILL.md (and linked reference/template/script files via |
| skill_manageA | Create / edit / patch / delete a skill, or write/remove a skill's linked file (governed — every write is policy-gated + audited). |
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 13 tools
Most tools have distinct purposes, but there is potential confusion between grep/glob (content vs filename search) and search_compliance_docs/session_search (both are search operations over different corpora). Descriptions are clear enough to differentiate in most cases.
Naming conventions are mixed: single verbs (read, write, edit), verb_noun with underscores (search_compliance_docs, ingest_to_rag), noun_verb without underscores (session_search, skills_list), and concatenated forms (listdir). This inconsistency makes it harder to predict tool names.
13 tools is within a reasonable range, but the set covers several domains (filesystem, RAG, sessions, skills) and includes redundant file operations (bash could substitute for many). Each tool has a purpose, but the count feels slightly heavy for a cohesive server.
The core workflows are covered: file CRUD, RAG ingest/search, session search, and skill management. Minor gaps exist (e.g., no explicit file delete, no RAG collection listing), but these can be worked around with bash or are outside the apparent primary scope.