get_decision
One decision by id, with its reference, kind, title, context, the options weighed, what was decided, consequences, status, the day decided, deciders and the decision it supersedes.
Return one decision: its reference, kind, title, the context it was taken in, the options weighed in order with their pros and cons, what was decided, what follows, where it stands, the day it was decided, who decided and the earlier decision it replaces. Read it when a story, a context pack or a conversation names a decision by reference and you need the exact choice and its reasoning before you build on it.
A decision of a project the token may not see, or any decision read through a guest token, is unknown rather than forbidden.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same actions as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
It reads and never changes anything.
Arguments
decision_id*stringUUID of the decision to fetch.
What it returns
{ "data": { "id": "a8b9c0d1-e2f3-4a4b-9c5d-6e7f8a9b0c13", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "number": 5, "reference": "CRM-DEC-5", "kind": "architecture", "title": "Keep the loyalty ledger in Postgres", "context": "<p>The ledger must be queried with the orders and audited.</p>", "options": [ { "title": "A ledger table in the main Postgres database", "pros": "One backup, one transaction, one place to audit", "cons": "Table growth needs partitioning within two years" }, { "title": "A dedicated event store", "pros": "Append-only by design", "cons": "A second system to run and to secure" } ], "decision": "<p>The ledger lives in Postgres, partitioned by month from the first release.</p>", "consequences": "<p>The reporting queries join the ledger directly.</p>", "status": "accepted", "decided_on": "2026-11-04", "deciders": ["c3d4e5f6-a7b8-4c9d-8e0f-1a2b3c4d5e6f"], "supersedes_id": "b9c0d1e2-f3a4-4b5c-8d6e-7f8a9b0c1d24", "supersedes_reference": "CRM-DEC-2", "position": 4, "created_at": "2026-10-28T09:20:00+00:00", "updated_at": "2026-11-04T15:00:00+00:00" }}How it fails
RESOURCE_NOT_FOUNDunknown decision_id, a decision of a project outside the token's scope or the person's visibility, or any decision read through a guest token.
TOKEN_MISSING_ABILITYtoken lacks decision:view.
How is this guide?
Last updated on