Skip to main content
Glama
sdcgovernance

sdcgovernance

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_governance_statusB

Report which governance dimensions the model defines. Returns model_id, model_label, has_governance, and active dimensions.

get_allowed_transitionsA

Get valid next states from the current workflow state. Returns list of valid transitions with target state info and path(s).

evaluate_transitionB

Evaluate whether a specific workflow transition is permitted. Returns PERMIT/DENY/INDETERMINATE with receipt.

validate_governanceB

Full governance validation of an instance against its model. Returns decision, has_governance, errors, dimensions_validated.

record_provenanceC

Record a provenance event as a W3C PROV-O record. Returns the PROV record content.

evaluate_decisionA

Evaluate a DMN decision table against instance context. Name the table by table_id (and table_version; the highest registered version when omitted) for a governed evaluation, or pass it inline as table_json for an ad-hoc one. Returns decision, matched_rules, reasoning, errors, the table's identity and content hash, and a tamper-evident Receipt whose receipt_hash covers table_id, table_version and table_hash as well as context_hash. instance_path is optional: when omitted, the decision is evaluated against extra_context alone, which is the path external context-only consumers (e.g. MTCP Evidence Packs) should use. Pass previous_hash to chain receipts; the caller is responsible for chain persistence.

register_decision_tableA

Register a decision table under a stable table_id and an immutable version, so evaluate_decision can name it and every Receipt it produces records which policy version applied. Returns table_id, version, table_hash (SHA-256 of the table's RFC 8785 canonical JSON), domain and policy. Registering the same content again under the same id and version is a no-op; different content under an existing id and version is refused: register it as a new version. Persists to the server's tables directory when one is configured.

list_decision_tablesA

List the registered decision tables: table_id, version, table_hash, domain, policy and registered_at for each version, lowest version first. Filter by table_id or domain. With table_id the full table JSON of each version is included, which is how a receipt's table_id and table_version are resolved back to the rules that applied.

verify_evidence_packA

Verify the integrity of an MTCP Evidence Pack by recomputing its evidence_pack_hash. Returns valid (bool), computed_hash, and expected_hash. Canonicalization follows RFC 8785: keys sorted, no whitespace, comma-colon separators, UTF-8.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct resource and action, but there are two close pairs: get_allowed_transitions vs evaluate_transition (enumerate vs decide) and get_governance_status vs validate_governance (report dimensions vs validate an instance). Descriptions do make the boundaries explicit, so misselection risk is low but non-zero.

Naming Consistency5/5

All nine tools follow a strict verb_noun snake_case pattern (evaluate_*, get_*, validate_*, record_*, register_*, list_*, verify_*). The repeated verbs are used semantically consistently, with no camelCase or bare-noun outliers.

Tool Count5/5

Nine tools is squarely in the well-scoped range and each maps to a concrete governance step: policy registration, policy lookup, decision evaluation, governance validation, transition discovery/authorization, provenance, and evidence verification. No filler or duplicate tools.

Completeness4/5

Core lifecycle is covered: register/list/evaluate decision tables, validate governance, inspect and evaluate transitions, verify evidence packs. Gaps remain around provenance (record only, no read/query tool), no evidence pack construction (verify only), and no deprecation/removal for registered tables, but these are workaroundable rather than blocking.

Maintenance

ActivityNo data
ResponsivenessOutdated data