QAE-Claude-mcp-example
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| certify_actionA | Evaluate the safety of an action across multiple constraint dimensions. This tool uses the QAE safety kernel to assess whether a proposed action is safe to execute. It returns a certificate with a decision (Certified, CertifiedWithWarning, EscalateToHuman, or Blocked) and detailed margins for each constraint dimension. Args: action_id: Unique identifier for the action (e.g., "act_123") agent_id: Identifier of the agent proposing the action (e.g., "claude_v3") scope: Scope dimension [0, 1], where 0=narrow, 1=global reversibility: Reversibility dimension [0, 1], where 0=permanent, 1=easily reversible sensitivity: Sensitivity dimension [0, 1], where 0=low-impact, 1=high-impact description: Optional human-readable description of the action Returns: Dictionary with keys: - decision: "Certified", "CertifiedWithWarning", "EscalateToHuman", or "Blocked" - zone: "Safe", "Caution", or "Danger" - margins: Dict of dimension -> margin value [0, 1] - binding_constraint: Name of most restrictive constraint (if any) - drift_budget: Remaining budget after this certification - certificate_id: Unique certificate identifier - deterministic_hash: SHA256 hash of the certificate - timestamp: ISO 8601 timestamp - description: Echo of input description (if provided) Example: >>> certify_action( ... action_id="act_deploy_algo", ... agent_id="claude_sales", ... scope=0.7, ... reversibility=0.4, ... sensitivity=0.8, ... description="Deploy new recommendation algorithm to 10% of users" ... ) |
| check_budgetA | Check the current safety budget utilization. This tool returns the current state of the safety budget, including:
Returns: Dictionary with keys: - budget_limit: Total safety budget [tokens/actions] - budget_used: Amount consumed in current period - budget_remaining: budget_limit - budget_used (clamped to >= 0) - rate_limit: Maximum certifications per period - total_certifications: Total number of certifications performed - utilization_percent: (budget_used / budget_limit) * 100 - timestamp: Current time (ISO 8601) |
| get_certification_historyA | Retrieve the recent certification history. This tool returns a list of recent certifications, most recent first. The history includes decision, zone, timestamp, and other metadata. Up to 50 certifications are stored; older ones are discarded. Args: limit: Maximum number of certifications to return (default 10, max 50) Returns: Dictionary with keys: - certifications: List of recent certification summaries - total_count: Total certifications in history - timestamp: Current time (ISO 8601) Each certification entry contains: - certificate_id: Unique certificate identifier - action_id: Action that was certified - agent_id: Agent that proposed the action - decision: Final decision ("Certified", "CertifiedWithWarning", etc.) - zone: Risk zone ("Safe", "Caution", "Danger") - timestamp: When the certification occurred - description: Optional action description |
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 3 tools
The three tools have clearly distinct purposes with no overlap: certify_action evaluates safety for proposed actions, check_budget monitors budget utilization, and get_certification_history retrieves past certifications. Each tool serves a unique function in the safety certification workflow, making selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern: certify_action, check_budget, and get_certification_history. The naming convention is uniform throughout, using clear action verbs followed by specific nouns that describe the tool's function.
Three tools is reasonable for a safety certification server, covering core operations: certification, budget checking, and history retrieval. While slightly minimal, each tool earns its place, and the count aligns well with the server's focused purpose without being overly sparse.
The tool set provides complete coverage for the safety certification domain: certify_action handles the primary certification operation, check_budget manages budget monitoring, and get_certification_history offers audit capabilities. This covers the essential lifecycle of certification, budget tracking, and historical review with no obvious gaps.