api-governance

get_decision_details

Read-only

Retrieve a PAST CodeRifts decision by decision_id (or fingerprint): full report payload, breaking changes list, scores, and linked receipt metadata if stored.

Use this when:

You have a decision_id (or fingerprint) from a previous preflight, PR comment, or CI log and need to inspect or explain that past decision.
You are auditing why a prior ALLOW/WARN/BLOCK was issued.
You are NOT requesting a new analysis of current before/after specs.

Do not use when:

You need a decision for the CURRENT uncommitted or PR head change set — call coderifts.preflight_change_set with the current artifacts.
You hold a receipt token and only need cryptographic/lifecycle verification — use coderifts.verify_receipt.
You have no decision_id/fingerprint — run preflight first to create one.

Inputs: at least one of decision_id (preferred) or fingerprint is required (empty {} is rejected by the server as INVALID_INPUT). Returns the stored decision document or not_found.

Scoping — fingerprint lookup returns only YOUR OWN decisions. A fingerprint is derived from content, not from an account, so two callers who preflight byte-identical specs derive the same one; the lookup is therefore constrained to the decisions your credential can prove it owns.

A decision that exists but is not yours returns the SAME not_found as one that was never issued. This is deliberate: a distinguishable "exists but forbidden" would confirm to any caller that a given content hash had been decided on by someone, which is the fact the scoping exists to withhold. Do not read not_found as proof that no such decision exists anywhere.

Decisions persisted without context.repository cannot currently be attributed to an account, and are not retrievable by fingerprint at all — not by their owner either. Retrieve those by decision_id, which is unchanged and unscoped. This is a limitation of what older stored rows carry, not a property of the lookup: rows written from now on record the account directly, so the gap narrows as older rows age out. If a fingerprint you expect returns not_found, use the decision_id before concluding the decision is missing.

When the stored envelope carries control fields, control_envelope.next_agent_step is structured remediation guidance the agent MAY follow for non-CONTINUE execution_action values (null on CONTINUE*). Still branch on execution_action; next_agent_step is a suggestion, not permission.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`decision_id`	No	The decision_id from a prior decision_result envelope. Provide this and/or fingerprint (at least one non-empty string required).
`fingerprint`	No	A verdict fingerprint (sha256:...); returns the latest matching decision. Provide this and/or decision_id (at least one non-empty string required).

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	Yes
`decision`	No
`evidence`	No
`patterns`	No
`operation`	No
`timestamp`	No
`risk_score`	No
`receipt_kind`	No
`chain_receipt`	No
`preflight_mode`	No
`safe_for_agent`	No
`decision_result`	Yes	decision-result.v1 envelope (control enums closed). Additive fields may appear and are not permission. Full schema: https://coderifts.com/schemas/decision-result.v1.consumer.json (producer: https://coderifts.com/schemas/decision-result.v1.producer.json).
`pattern_sources`	No
`breaking_changes`	No
`control_envelope`	No	Control envelope (control/1.0) derived from the stored decision_result. Includes next_agent_step (structured remediation SUGGESTION for non-CONTINUE execution_action; null on CONTINUE*; not permission — still branch on execution_action).
`evidence_quality`	No
`execution_action`	No
`coderifts_version`	No
`requires_migration`	No
`verdict_fingerprint`	No
`required_action_core`	No	Branchable required-action core { type, reason_code, recheck_required } when present on the envelope.
`decision_spec_version`	No
`decision_semantic_hash`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 24, 2026

changedOutput schema / properties / decision_result / properties / derivation / description

Previous value: -"ID637 6b additive. Present only when derivation:\"server\" produced this envelope. { source: github_compare, base_sha, head_sha }. Covered by body_hash; not fingerprint."New value: +"ID637 6b additive. Present only when derivation:\"server\" produced this envelope. { source, platform?, base_sha, head_sha }. Covered by body_hash; not fingerprint."

Changed1 schema field changedAug 23, 2026

addedOutput schema / properties / decision_result / properties / derivation

Added value: +{
+  "description": "ID637 6b additive. Present only when derivation:\"server\" produced this envelope. { source: github_compare, base_sha, head_sha }. Covered by body_hash; not fingerprint.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed2 schema fields changedAug 23, 2026

addedOutput schema / properties / decision_result / properties / audience
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / decision_result / properties / authority

Added value: +{
+  "description": "ID963 additive. { audience, tenant_scope: bound|unbound, binding_proven_at? }. Informational — not permission, not a verify-receipt gate, not an ACL.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedAug 23, 2026

addedOutput schema / properties / decision_result / properties / blast_radius

Added value: +{
+  "description": "ID27 additive COUNTS (not a score). Not permission.",
+  "properties": {
+    "consumers_declared": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "consumers_observed": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "endpoints": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "fields": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "graph_source": {
+      "type": "string"
+    },
+    "params": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedAug 22, 2026

addedOutput schema / properties / decision_result / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / decision_result / description

Previous value: -"decision-result.v1 envelope (present when a chain receipt is available). Full schema: https://coderifts.com/schemas/decision-result.v1.consumer.json"New value: +"decision-result.v1 envelope (control enums closed). Additive fields may appear and are not permission. Full schema: https://coderifts.com/schemas/decision-result.v1.consumer.json (producer: https://coderifts.com/schemas/decision-result.v1.producer.json)."

addedOutput schema / properties / decision_result / properties

Added value: +{
+  "base": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "decision": {
+    "enum": [
+      "ALLOW",
+      "WARN",
+      "REQUIRE_APPROVAL",
+      "BLOCK"
+    ],
+    "type": "string"
+  },
+  "decision_body_hash": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "decision_id": {
+    "type": "string"
+  },
+  "environment": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "execution_action": {
+    "enum": [
+      "CONTINUE",
+      "CONTINUE_WITH_MONITORING",
+      "REQUEST_APPROVAL",
+      "STOP"
+    ],
+    "type": "string"
+  },
+  "expires_at": {
+    "type": "string"
+  },
+  "fingerprint": {
+    "type": "string"
+  },
+  "head": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "input_fingerprint": {
+    "type": "string"
+  },
+  "operation": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "receipt": {
+    "type": "object"
+  },
+  "repository": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "safe_for_agent": {
+    "type": "boolean"
+  },
+  "spec_version": {
+    "pattern": "^decision-result\\.v1(\\.[0-9]+)?$",
+    "type": "string"
+  }
+}

Changed13 schema fields changedAug 21, 2026
- addedOutput schema / properties / chain_receipt
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / coderifts_version
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / decision_semantic_hash
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / decision_spec_version
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / evidence
```
Added value: +{
+  "type": [
+    "object",
+    "array",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / evidence_quality
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / meta / properties / omitted_sections
```
Added value: +{
+  "type": "array"
+}
```
- addedOutput schema / properties / operation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / pattern_sources
```
Added value: +{
+  "type": "array"
+}
```
- addedOutput schema / properties / preflight_mode
```
Added value: +{
+  "enum": [
+    "analyze",
+    "authorize"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / receipt_kind
```
Added value: +{
+  "enum": [
+    "NONE",
+    "operation_authorization"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / requires_migration
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / timestamp
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 17, 2026

changedOutput schema / properties / control_envelope / description

Previous value: -"Control envelope (control/1.0) derived from the stored decision_result."New value: +"Control envelope (control/1.0) derived from the stored decision_result. Includes next_agent_step (structured remediation SUGGESTION for non-CONTINUE execution_action; null on CONTINUE*; not permission — still branch on execution_action)."

First observedAug 12, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, but the description adds substantial non-obvious behavior: fingerprint scoping to own decisions, deliberate identical not_found for forbidden lookups, legacy rows not retrievable by fingerprint, and the meaning of control_envelope.next_agent_step. This goes well beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections and front-loaded purpose, but it is quite lengthy and includes some details that slightly overlap with the schema (e.g., empty {} rejection) and an extended legacy-row explanation that could be tightened. Still, nearly every sentence carries useful behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (scoped lookups, legacy limitations, not_found semantics, control_envelope hints), the description covers all critical aspects an agent needs to call it correctly. The presence of an output schema means return-value details do not need to be in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema has 100% parameter coverage, the description adds meaningful semantics beyond it: decision_id is preferred, fingerprint is content-derived and scoped to the caller's own decisions, decision_id is unscoped, and a fallback strategy is provided when fingerprint returns not_found. This enhances the agent's ability to choose and combine the parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Retrieve'), a clear resource ('a PAST CodeRifts decision'), and the key identifiers (decision_id or fingerprint). It explicitly enumerates what the payload contains (report, breaking changes, scores, receipt metadata) and distinguishes itself from sibling tools by focusing on past decisions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'Use this when' and 'Do not use when' sections, naming the exact alternatives (preflight_change_set, verify_receipt) and the conditions that trigger them. This is the clearest possible routing guidance for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All api-governance tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

preflight_change_set is the sole creation/analysis entry point, get_decision_details is explicitly for retrieving past decisions, and verify_receipt is for validating an already-held receipt. Their descriptions include cross-references and negative usage guidance that make the boundaries unambiguous.

Naming Consistency5/5

All three tool names follow a consistent snake_case verb_noun pattern: preflight_change_set, get_decision_details, verify_receipt. There are no mixed conventions or vague verbs.

Tool Count5/5

Three tools map cleanly to the core governance workflow: create/analyze a change set, inspect a past decision, and verify a receipt before acting. The count is well-scoped and each tool earns its place.

Completeness5/5

The set covers the full decision lifecycle for its stated domain: preflight produces decisions/receipts, get_decision_details retrieves historical decision records, and verify_receipt validates current authorization. Decisions are immutable and revocation is checked via receipt validity, so no obvious lifecycle step is missing.

get_decision_details

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources