Weio Evidence Checks
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_production_provenanceB | Closed-world consistency comparison of caller-supplied release identifiers and digests. PASS is not live observation, independent proof, authenticity verification, or production approval. |
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 1 tool
With only one tool, there is no possibility of misselection or overlapping purpose. The tool's scope is clearly stated as closed-world consistency comparison of caller-supplied identifiers and digests.
The single tool name verify_production_provenance follows a consistent verb_noun pattern and is self-explanatory. No other tool names exist to create inconsistency.
A single tool is too thin for a server named 'Weio Evidence Checks', which suggests multiple evidence or provenance checks. The count feels under-scoped and leaves no room for related verification operations.
The tool only compares caller-supplied release identifiers and digests, explicitly excluding live observation, independent proof, authenticity verification, and production approval. For an evidence-checking server, this leaves significant gaps in lifecycle coverage and real verification capability.