assay-mcp-server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assay_check_argsC | Validate tool arguments against a policy schema. |
| assay_check_sequenceC | Validate if a tool call is allowed given the history. |
| assay_policy_decideC | Check if a tool is blocked by policy. |
| assay_check_coverageC | Analyze trace coverage against a policy. |
| assay_explain_traceC | Explain trace evaluation against a policy |
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 aspect of policy analysis: argument validation, coverage, sequence validation, trace explanation, and policy decision. No overlap in purpose.
All tools follow the consistent pattern 'assay_<verb>_<noun>', using snake_case throughout. The prefix 'assay_' unifies the set.
Five tools is a well-scoped set for a policy analysis server. Each tool serves a clear role without redundancy, covering the core operations.
The tools cover essential policy checking operations (validate args, check coverage, sequence validation, explain traces, decide policy). Missing a tool to list or retrieve policies, but the set is otherwise solid for its domain.