PADC Evidence Lab
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesB | List current trusted source revisions and declared text-surface completeness. |
| find_evidenceC | Search trusted page-indexed source text. Excerpts and page numbers are derived by the server; the agent cannot supply either field. |
| run_document_reviewC | Run a server-side PAGE_INDEXED_TEXT review protocol for an exact claim.
|
| validate_evidence_assessmentB | Validate structural admissibility and persist every attempt. Passing means STRUCTURALLY ADMISSIBLE PROPOSAL FOR ; it does not semantically adjudicate the claim. NE is bound to a server-derived MissingnessRecord. |
| build_evidence_matrixC | Build a current-collection-scoped audit matrix.
|
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 phase of the evidence workflow: source listing, evidence search, document review, assessment validation, and matrix building. The descriptions clarify non-overlapping boundaries, especially around server-derived fields and structural versus semantic validation.
All names use a consistent snake_case verb_noun pattern: list_sources, find_evidence, run_document_review, validate_evidence_assessment, build_evidence_matrix. No mixed conventions or vague verbs appear.
Five tools is well-scoped for a specialized evidence-lab server. Each tool has a clear, non-redundant role in the workflow, and the count avoids both thinness and bloat.
The surface covers the core evidence lifecycle from listing sources through search, review, validation, and matrix building. Minor gaps exist around source ingestion/management and semantic query execution, though the latter is explicitly deferred in the version notes.