Annsa

annsa_spec

Read-only

The plan for one priority. Use it before starting work: it gives you the Problem, What to build, and the Done When lines you'll have to prove. The reply carries build_id, the spec id (build_…) that verify and ship take as spec_id. Add include_evidence to see Evidence and direction, Files to touch and the customer quotes behind it. It doesn't list or rank priorities; that's annsa.priorities.

Input Schema

Name	Required	Description
`batch`	No	Export many specs at once, filtered by spec_ids, stage or since.
`label`	No	What to call this session, up to 60 characters. Shown as who did it.
`limit`	No	With batch: how many specs. Defaults to 10, max 50.
`since`	No	A date like 2026-11-06, or 'last month'.
`stage`	No	With batch: only specs at this stage: open, ready, building, shipped, shared or closed.
`until`	No	A date like 2026-11-06. With since, the window.
`format`	No	With batch: list (one line each, the default) or full (the whole spec).
`status`	No	With batch: the spec's status: open, ready, building, shipped, shared, closed or done. Not the board stage; that's stage.
`include`	No	One extra: repo_rules (the repo's agent files), decision (the Decision text), memory (related memory) or verification (the verify receipts).
`reached`	No	With batch: only specs that reached staging, main or prod, newest first.
`spec_id`	No	The spec id (build_…), instead of a priority.
`spec_ids`	No	With batch: the specs to export (up to 50).
`investigate`	No	Add an analysis of the problem from the feedback and history.
`priority_id`	No	The long id, instead of priority_number.
`include_memory`	No	Add related answers and what earlier work learned.
`include_history`	No	Add notes from earlier work on related priorities.
`priority_number`	No	The # number, e.g. 20 for #20.
`include_evidence`	No	Add the Evidence and direction and Files to touch sections, and the customer quotes.
`include_feedback`	No	With investigate: add customer quotes.
`include_direction`	No	Add the opening of each Direction page that applies.
`include_principles`	No	Add the full text of the principles that apply.

Output Schema

Name	Required	Description	Default
`who`	No
`record`	No
`message`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedNov 8, 2026

addedInput schema / properties / batch / description

Added value: +"Export many specs at once, filtered by spec_ids, stage or since."

changedInput schema / properties / format / description

Previous value: -"With batch: list is one line each; full is the whole spec."New value: +"With batch: list (one line each, the default) or full (the whole spec)."

changedInput schema / properties / include / description

Previous value: -"repo_rules adds the repo's agent files."New value: +"One extra: repo_rules (the repo's agent files), decision (the Decision text), memory (related memory) or verification (the verify receipts)."

changedInput schema / properties / include_direction / description

Previous value: -"Direction first screens"New value: +"Add the opening of each Direction page that applies."

changedInput schema / properties / include_evidence / description

Previous value: -"Adds Evidence and direction, Files to touch and the quotes"New value: +"Add the Evidence and direction and Files to touch sections, and the customer quotes."

addedInput schema / properties / include_memory / description

Added value: +"Add related answers and what earlier work learned."

changedInput schema / properties / include_principles / description

Previous value: -"The rules in full"New value: +"Add the full text of the principles that apply."

addedInput schema / properties / investigate / description

Added value: +"Add an analysis of the problem from the feedback and history."

addedInput schema / properties / label / description

Added value: +"What to call this session, up to 60 characters. Shown as who did it."

changedInput schema / properties / limit / description

Previous value: -"Max 50"New value: +"With batch: how many specs. Defaults to 10, max 50."

addedInput schema / properties / reached

Added value: +{
+  "description": "With batch: only specs that reached staging, main or prod, newest first.",
+  "enum": [
+    "staging",
+    "main",
+    "prod"
+  ],
+  "type": "string"
+}

changedInput schema / properties / since / description

Previous value: -"ISO date or 'last month'"New value: +"A date like 2026-11-06, or 'last month'."

changedInput schema / properties / stage / description

Previous value: -"With batch: only specs at this stage."New value: +"With batch: only specs at this stage: open, ready, building, shipped, shared or closed."

addedInput schema / properties / status / description

Added value: +"With batch: the spec's status: open, ready, building, shipped, shared, closed or done. Not the board stage; that's stage."

addedInput schema / properties / until / description

Added value: +"A date like 2026-11-06. With since, the window."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "record": {
+      "type": "object"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "who": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 6, 2026

TDQS

Score is being calculated.

All Annsa tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?