Vigile
SearchContents

DocumentationOperations

list_decisions

List decisions by ID, optionally filtered by status. Includes standalone decisions and withdrawn records. Each names the projects and tasks it affects. Returns at most 100 per call.

The operation's own description: what an agent reads to decide whether and how to call it.
It
Reads. It changes nothing.
Who may call it
Every user.
Pages
Answers in pages of at most 100, with a continuation token for the next.
Answers with
A list of decisions, each in short. Its fields: kind, id, title, status, version, affects, and sometimes deleted_at. Not in it: description, why, links, timeline, created_at, created_by, updated_at and unchanged_since. get has those.
MCP tool
list_decisions
HTTP
POST /api/list-decisions
Command
vigile list-decisions

Input

FieldTakesWhat it is
status"proposed" | "active" | "withdrawn"optional
continuationstringoptionalThe continuation token from the previous page. Return it unchanged to the same operation with the same filters; stop when no token is returned.

A field that is not listed here is refused, as invalid_input. On the command line each field is an option, with hyphens for underscores: --status.

Example

The same call three ways, as agent1. It was made on the demo plan after a few changes that set the scene. Over HTTP and MCP, a call without a key acts as agent1 on a new instance.

Command line

vigile list-decisions --status active --as agent1

HTTP

curl -s http://127.0.0.1:8700/api/list-decisions \
  -H 'content-type: application/json' \
  -d '{"status":"active"}'

MCP tool call

{
  "name": "list_decisions",
  "arguments": { "status": "active" }
}

The answer

{
  "decisions": [
    {
      "kind": "decision",
      "id": "018",
      "title": "Show gross prices",
      "status": "active",
      "version": 1,
      "affects": []
    }
  ]
}

This is what a service answered when this page was built. Over HTTP it is the body of the response, over MCP the text of the tool result, and the command line prints it in words unless given --json.

What it answers

One page of decisions in ID order, optionally filtered by state. Standalone records are discoverable without a project or task.

Rules

Use the continuation token with the same filters to read the next page. Withdrawn records are included unless filtered out; deleted records are not listed.

Errors

invalid_input means the state or continuation token is invalid.