One release and its readiness, feature by feature, worked out from the board by the rules of D113 (never by AI).
get_releaseOne release and its readiness, feature by feature, worked out from the board by the rules of D113 (never by AI).
Feature = an epic in the release; issues with no epic are grouped as other. Each feature lists the checks it passes and, when it is not Ready, the reasons. For people who do not manage releases (manage: false) the gate items, baseline and scope history are left out — frontmatter.gate is [], baseline null, scope_log [] and gate / scope are null — only gate_summary is given, and added_after_baseline is false (D113 (4)). D198: everyone sees frontmatter.release_note and frontmatter.deployments; in the member view each deployment's notes is "" and build_url null. latest_deployments = what is live in each environment. Use the numbers as they are; do not guess.
Read this before answering anything about a release ("are we ready?", "what is blocked?", "summarise for the steering meeting"). Use status, features[] (status, checks, reasons), other, counts, gate_summary and scope exactly as returned — never guess, round or invent numbers, and name the issue keys from reasons. manage: false is the member view (no gate items, no scope history; each deployment's notes is "" and build_url null) — say so rather than guessing them. frontmatter.release_note is the customer-facing release note (apart from body, the internal description) and frontmatter.deployments the log of recorded deployments (D198); latest_deployments = what is live in each environment — report them as returned, never guess what is live. You may create a planned release (create_release) and edit its name, date, milestones and description until the baseline is locked (update_release), write its release note while it is planned, and record deployments (add_release_deployment), with your user's rights (D189, D198). You cannot tick its gate, lock its baseline, mark it shipped, reopen or delete it: that is for people in the web app — an AI agent never approves a release.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_key": "<project_key>",
"release_id": "<release_id>"
},
"name": "get_release"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| release_id | Yes | Release id (spec D113): `R-` + a number, unique in its project; the file is `releases/R-{n}.md`. | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |