Skip to main content
Glama

Server Details

The plan your AI agents work from. Project management and customer feedback for agent teams.

Ownership verified
Status
Healthy
Uptime
9.7% over 25 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

C2.7/5.0

Scored across 8 tools

Disambiguation2/5

Several tools are broad umbrellas with overlapping territory: annsa_ask can read feedback, docs, surveys, customers, transcripts, accounts and templates, which overlaps annsa_priorities and annsa_spec (also reads). On the write side, annsa_board ('Arrange the board'), annsa_work ('Do the work on a priority'), annsa_file ('Add feedback, a finding, a priority...') and annsa_decide all mutate the same board/priority objects with vague, literary boundaries that an agent will struggle to resolve.

Naming Consistency3/5

There is a strong, consistent `annsa_` prefix with snake_case throughout, which helps. However, the suffix mixes action verbs (ask, decide, file, share, work) with object nouns (board, priorities, spec), so there is no predictable verb_noun convention mapping name to action.

Tool Count4/5

Eight tools sits comfortably in the well-scoped 3-15 range and avoids bloat. The caveat is that each tool packs many sub-operations, so the count is low relative to the actual action surface.

Completeness4/5

The lifecycle is largely covered: capture feedback (file), organize (board), set principles (decide), rank (priorities), spec (spec), execute (work), and notify customers (share), plus broad reads via ask. Missing delete/archive, feedback merge/update, and survey/template management are minor gaps agents can work around.

Available Tools

8 tools
annsa_ask
Read-only
Inspect

Ask Annsa a question in plain words. Use it to find what customers said about something, what's on the board, or how Annsa works. about picks where to look: feedback (default), annsa (the docs), surveys, customer, accounts, templates or transcript. You get an answer with the quotes and priorities it came from. Before filing a bug, send do_we_have with your text to check whether a priority already covers it. It doesn't list the ranked work; that's annsa.priorities.

NameRequiredDescriptionDefault
daysNoWith about=surveys: how many days of replies to count (1 to 365, default 30).
fromNoWith do_we_have: customer (a customer's words) or agent (an agent's finding).
pageNoFor a long transcript: which page, starting at 1.
aboutNoWhere to look: feedback (default), annsa (the docs), surveys, customer, accounts, templates or transcript.
skillNoReturns a skill file instead of an answer: working, spec-skill, decisions or welcome. No question needed.
accountNoWith customer: which company, if the name matches more than one.
customerNoWith about=customer: their name, email or id.
questionNoWhat you want to know, in a sentence.
do_we_haveNoThe text you're about to file. Returns the nearest priorities, each judged same, possibly or different.
project_idNoOnly search one project's feedback.
transcriptNoWith about=transcript: which call, like t12 or its id. Long ones come in pages.
have_versionNoWith skill: the version of the copy you already have, so you only get it if it changed.
include_archivedNoWith about=surveys: include archived surveys.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_board
Destructive
Inspect

Tidy the board. Use it to change a priority's stage or severity, merge duplicates, move priorities between groups, fix a title, place priorities on a bet, or cut a release. A merge retires the duplicate numbers for good. Some actions, like park and assign, are for people only. It doesn't do the work on a priority; that's annsa.work.

NameRequiredDescriptionDefault
atNoFor cut: the release date.
opNoFor bet: 'list', 'create' (title and metric_label; agents last), 'update' (bet_id), 'delete', 'reorder' (bet_ids) or 'place' (priority_ids). For direction: 'get', 'list', 'update' (document_text and reason), 'comment' (thread_id), or 'approve' and 'dismiss' (document_id and reason; a person's). For cut: 'publish', with release_number, channel and the live annsa.ai url. It marks the release's rows Shared and sends nothing. For view: 'list', 'create', 'update', 'delete', or 'keep' and 'dismiss' (a person's).
urlNoFor cut op=publish: the live changelog link.
intoNoFor merge: the priority that stays.
rankNoFor a bet: its place in the list, 1 is top; the others move down.
itemsNoFor regroup: the new group for each priority.
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
picksNoFor pick: priorities in order, each with a line on why.
quoteNoFor direction op=comment: the line you're replying to.
sinceNoFor cut: the start of the window the release covers.
stageNoFor set_stage: open, ready or closed.
titleNoFor bet or view: its title.
untilNoFor cut: the end of that window.
actionYesset_stage: Move a priority to open, ready or closed. assign: Set who a spec is assigned to. A person's action. correct: Fix a title, detail or ruled-out entry. The old wording is kept. park: Take a priority off the list, with a reason, until someone unparks it. A person's action. unpark: Put a parked priority back on the list. retract: Unfile feedback, or mark a shipped priority as not shipped. A person's action; without confirm it only shows the plan. regroup: Move priorities between groups; the reply carries the undo. merge: Fold duplicate priorities into one. Their numbers are retired for good. Shipped priorities can't be merged. bet: List, create, update, delete or reorder bets, or place priorities on one. op says which. direction: Read, list, update or comment on a Direction page. op says which. set_severity: Set a priority's severity, P0 to P3. From an agent it's a proposal and needs a reason; a person's typed severity wins. cut: Close a release and write its changelog. op=publish marks its rows Shared. pick: Set a person's short list of priorities, in order. approve_findings: Let through agent findings held back by the daily limit. The owner's action. view: Save a board view. An agent's is a suggestion until a person keeps or dismisses it.
bet_idNoFor bet update, delete or place: which bet.
bucketNoFor a bet: the group it counts toward, like Product or GTM.
doc_idNoWhich Direction page; leave it out for the Overview.
parentNoThe priority this one sits under. For bet op=place: the bet.
personNoThe email or user id of the person whose words they are.
reasonNoWhy, in a line. Needed for retract, correct, merge and an agent's severity.
recipeNoFor view: the annsa.priorities arguments the view runs.
aim_pctNoFor a bet: how much of your effort it should get, 0 to 100.
bet_idsNoFor bet reorder: every bet's id, best first.
channelNoFor cut op=publish: changelog or marketing.
commentNoFor direction op=comment: your words.
confirmNoFor retract: true to do it. Without it the reply only shows what would change.
spec_idNoFor assign and retract: the spec id.
view_idNoFor view update or delete: which view, from view op=list.
why_nowNoFor a bet: why it matters now, in a line.
evidenceNoFor direction op=update: the evidence behind the change.
originalNoFor correct: the old category, or the ruled-out entry being replaced.
questionNoFor view: the question the saved view answers.
severityNo0 broken, 1 poor, 2 could be better, 3 minor. From an agent it's a proposal until a person sets it.
correctedNoFor correct: what it should say now.
doc_titleNoThe page title (kept if blank).
thread_idNoFor direction op=comment: the thread to reply in.
duplicatesNoFor merge: the priorities being folded into `into`.
assigned_toNoWho gets it: an agent (like claude-code or codex) or a person's email. Empty unassigns.
document_idNoFor direction approve or dismiss: which page.
park_reasonNoFor park: why, up to 500 characters.
priority_idNoThe long id, instead of priority_number.
allow_sharedNoFor retract: true to retract even after customers were told.
feedback_idsNoFor retract: the feedback rows to unfile.
metric_labelNoFor a new bet: what the measure is called.
metric_queryNoFor a computed bet: the name of Annsa's measure.
metric_valueNoFor a written bet: the number now. A person's.
person_wordsNoThe person's exact words, not a summary. Recorded as their quote.
priority_idsNoFor bet op=place or direction: the priorities.
document_textNoFor direction update: the page text, at least 50 characters.
metric_sourceNoFor a new bet: written (you type the number) or computed (Annsa measures it).
owner_user_idNoFor bet update: the owner's user id; none clears it.
expected_stageNoFor set_stage: only change it if the stage is still this: open, ready or closed.
release_numberNoFor cut op=publish: which release.
correction_typeNoFor correct: 'title', 'detail', 'ruled_out' or 'category'. 'category' is a person's; the old wording is kept.
priority_numberNoThe # number, e.g. 20 for #20.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_decide
Destructive
Inspect

Record what a person decided. A person uses it to answer a question an agent raised or sign off a priority. As an agent you can list principles, propose one, approve or dismiss a proposed spec change, or pass on a person's exact words with person_words. To ask a person something, use annsa.work escalate instead.

NameRequiredDescriptionDefault
opNoFor principle: 'list', 'propose' (an agent's), or 'write', 'retire' and 'activate' (a person's).
areaNoFor scope=area: the part of the product the rule covers.
takeNoFor sign with do_this: the option you chose, in a few words.
textNoFor direct or ask_back: the words.
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
scopeNoHow far the decision reaches: priority, area (needs area) or company. area or company also writes a principle.
titleNoFor principle: the rule's title.
topicNoFor principle: what the rule is about.
actionYesapprove: Accept another writer's proposed section text, by update_id. dismiss: Turn down a proposed section text; the current text stays. answer: Record a person's answer to the open ask on a priority. An agent passes on the person's exact words with person_words. Picking an option labelled Merge, Ship it, Park it or Retract the ship runs it; free text is only recorded. ask_back: A person asks the agent a question back on a priority. A person's action. direct: A person gives the agent holding a priority a direction; the agent reads it on its next reply. A person's action. choose: Record a person's pick on a Needs you question (send disagreement_id). One option, or neither. A person's action. sign: Record a person's decision on a priority (do_this, do_nothing, park or dismiss), with because. A person's action. principle: Your decision memory. Agents can list principles or propose one; a person writes, retires or reactivates them. A proposal applies at once.
answerNoFor choose: the option picked, or neither. For principle: the answer behind the rule.
optionNoFor answer: the option's label.
personNoThe email or user id of the person whose words they are.
becauseNoFor sign: why, in a sentence.
decisionNoFor sign: do_this, do_nothing, park or dismiss.
wrong_ifNoFor sign: what would show the decision was wrong.
principleNoFor principle: the rule, in a sentence.
ruled_outNoOptions you ruled out, one per entry as 'option — why'.
update_idNoFor approve or dismiss: the proposed change, from annsa.spec's updates.
may_decideNoFor sign: what the agent may decide on its own from here. Needs answered_by.
supersedesNoFor principle: the principle this replaces.
answered_byNoThe person who decided, when you're passing on their words.
priority_idNoThe long id, instead of priority_number.
person_wordsNoThe person's exact words, not a summary. Recorded as their quote.
principle_idNoFor principle retire or activate: which one, from principle op=list.
falsifier_dueNoFor sign: when to check wrong_if, like 2026-12-31.
while_waitingNoFor sign: what the agent may keep doing until the answer comes.
decision_untilNoFor sign: when this decision expires, like 2026-12-31.
must_come_backNoFor sign: what the agent has to bring back to a person.
disagreement_idNoFor choose: the id of the Needs you question, from the Needs you list.
priority_numberNoThe # number, e.g. 20 for #20.
review_conditionNoFor sign: when to look at this decision again, in a sentence.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_fileInspect

Add something new to the board. Use it to file what a customer said, a bug or finding you found, or an idea. It attaches to the matching priority if there is one; add stand_alone to make a new priority instead. The reply tells you which priority it landed on. It doesn't change rows that already exist; that's annsa.board. To tell the Annsa team about Annsa itself, use report.

NameRequiredDescriptionDefault
betNoThe bet a new priority goes on, by title or id; none if you leave it out.
skuNoFor add_transcript: the plan or product the customer is on.
fromNoWho said it: customer, team, agent, idea or roadmap.
lineNoFor submit from a scanner: the line number.
pathNoFor submit from a scanner: the file.
ruleNoFor submit from a scanner: the rule that fired.
textNoFor report, add_template, connect_goal and add_transcript: the words. submit takes feedback.
typeNoWhich kind: bug, feature, improvement, praise or question.
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
themeNoThe group it belongs to, one of the workspace's themes.
titleNoFor add_priority, add_page, add_template or report: the title.
actionYessubmit: File what a customer said or what you found. With priority_number it attaches to that priority; with stand_alone it starts a new one. report: Tell the Annsa team about a bug, gap or idea in Annsa itself. Send text; title names the tool and action. Keep your customers' data out of it. add_page: Make a page from a template, private to you. Returns the link. add_template: Save a template with a title, text and when to use it. {blanks} in the text become its fields. connect_goal: Answer the welcome's optional question about what you want from Annsa, up to 300 characters. Goes to the Annsa team, not your board. add_transcript: Add a call transcript as customer feedback. What the customer asked for is filed from it. A person's action. import_direction: Import a strategy doc in two steps. First preview its lines, then add the ones you pick as ideas. A person's action. add_priority: Add a priority from a title and detail, with no customer words.
detailNoFor add_priority: the longer words of the row, up to 20000 characters.
doc_idNoWhich Direction page. Leave it out for a new page, or the Overview.
fieldsNoFor add_page: a value for each {blank} in the template.
insistNoFor submit and add_priority: file it even if a matching priority exists.
parentNoThe priority this one sits under. For bet op=place: the bet.
reasonNoFor add_priority: why you're filing it, in a line.
sourceNoWhere the feedback came from, like intercom. Defaults to mcp.mcp
verdictNoFor submit on a shipped priority: still_broken or fixed. false_positive doesn't close the row.
feedbackNoFor submit: what was said, word for word.
severityNo0 broken, 1 poor, 2 could be better, 3 minor. From an agent it's a proposal until a person sets it.
templateNoFor add_page: the template's key, from annsa.ask about=templates.
call_typeNoFor add_transcript: interview, sales_call, support or other (the default).
doc_titleNoThe page's title. Kept if you send none.
referenceNoA link someone can follow: a PR, URL or log line. A finding needs one.
selectionNoFor import_direction: which lines to add, by title. Leave it out to add all.
with_specNoFor submit and add_priority: also write a ready spec and return its spec_id.
origin_refNoWhere it came from, like a ticket or file:line. The same one again adds to the same row.
root_causeNoThe cause in one line, shaped 'When ___, ___ can't ___ because ___'. Up to 300 characters.
adjudicatedNoTrue if a person checked this scanner finding; raw scanner output is refused.
priority_idNoThe long id, instead of priority_number.
proposal_idNoFor import_direction: the id the preview returned, to add the lines you picked.
stand_aloneNoFor submit: start a new priority from this row. Not with priority_number.
when_to_useNoFor add_template: when an agent should pick this template.
revenue_bandNoWhat the customer pays: an amount like 499, or a tier word.
customer_nameNoThe customer who said it.
document_textNoFor import_direction: the document, at least 50 characters.
customer_emailNoTheir email, if you have it.
priority_numberNoThe # number, e.g. 20 for #20.
severity_reasonNoWhy this severity, in a line.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_priorities
Read-only
Inspect

Your ranked to-do list. Use it to see what to work on next: every open priority in rank order, with how many customers asked and why each one ranks where it does. Ask for one priority by its number to get just that row. For the full plan behind a priority, read annsa.spec. It doesn't search what customers said; that's annsa.ask.

NameRequiredDescriptionDefault
betNoOnly priorities on this bet, by id. unplaced lists the ones no bet has yet.
mineNoOnly the priorities you're working on. The reply also counts what needs you.
typeNoOnly this kind: bug, feature, improvement, praise or question.
viewNoA saved view by name, or radar (what's rising, shipped and quiet) or brief.
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
limitNoHow many to return. Defaults to 5, max 100.
stageNoopen, ready, building, shipped, shared or closed. Leave it out for the ranked active priorities: open, ready and building.
topicNoA word or phrase to search for in priorities and their feedback.
offsetNoHow many priorities to skip, for the next page.
personNoA person's email. With picked, whose picked list.
pickedNoOnly the priorities a person picked; person says whose.
weeklyNoA summary of the week instead of the list: what's rising, what shipped, what went quiet.
windowNoHow far back the radar looks: 7d, 14d or 30d. Defaults to 7d.7d
includeNoExtra lists to include, comma separated: agents, to_verify, in_build, unrated_filings or all.
rank_byNoLeave it out for the board's order, the same as the app. Or rank by volume, urgency, revenue, retention (unhappy customers), delight (praise) or feature (new-feature asks).
segmentNoCustomer size: all (default), enterprise or smb.all
priority_idNoThe long id, instead of priority_number.
include_parkedNoInclude parked priorities too.
release_numberNoOnly the priorities in this release.
priority_numberNoThe # number, e.g. 20 for #20.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_share
Destructive
Inspect

Tell customers their request shipped. Use it after a priority ships to email or notify everyone who asked for it. Emails can't be unsent, so only a signed-in person can run it. The reply says who was told. It doesn't mark anything shipped; that's annsa.work ship.

NameRequiredDescriptionDefault
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
actionYesshare: Email or notify the customers who asked that it shipped. An email cannot be unsent.
channelNoWho to tell: email, widget (in the app), both (the default) or skip (nobody).
messageNoFor share: your own words, instead of the default note.
spec_idNoThe shipped spec, by id.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_spec
Read-only
Inspect

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.

NameRequiredDescriptionDefault
batchNoExport many specs at once, filtered by spec_ids, stage or since.
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
limitNoWith batch: how many specs. Defaults to 10, max 50.
sinceNoA date like 2026-11-06, or 'last month'.
stageNoWith batch: only specs at this stage: open, ready, building, shipped, shared or closed.
untilNoA date like 2026-11-06. With since, the window.
formatNoWith batch: list (one line each, the default) or full (the whole spec).
statusNoWith batch: the spec's status: open, ready, building, shipped, shared, closed or done. Not the board stage; that's stage.
includeNoOne extra: repo_rules (the repo's agent files), decision (the Decision text), memory (related memory) or verification (the verify receipts).
reachedNoWith batch: only specs that reached staging, main or prod, newest first.
spec_idNoThe spec id (build_…), instead of a priority.
spec_idsNoWith batch: the specs to export (up to 50).
investigateNoAdd an analysis of the problem from the feedback and history.
priority_idNoThe long id, instead of priority_number.
include_memoryNoAdd related answers and what earlier work learned.
include_historyNoAdd notes from earlier work on related priorities.
priority_numberNoThe # number, e.g. 20 for #20.
include_evidenceNoAdd the Evidence and direction and Files to touch sections, and the customer quotes.
include_feedbackNoWith investigate: add customer quotes.
include_directionNoAdd the opening of each Direction page that applies.
include_principlesNoAdd the full text of the principles that apply.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo
annsa_workInspect

Do the work on a priority. Use it to claim a priority, write your part of the spec, leave notes, prove each Done When line with verify, and mark it shipped. claim gives you a spec_id for write, verify and ship, and a holder_key for write and ship. Ship only records that it shipped; it doesn't deploy anything. If you need a person to decide something, use escalate. It doesn't move, merge or re-rank priorities; that's annsa.board.

NameRequiredDescriptionDefault
askNoFor escalate: the question you want the person to answer, in one line.
howNoFor verify: how you checked the line: test, staging, prod or manual.
intoNoFor resolve move_row: the priority the row moves to.
textNoThe note, or for write the whole new section, not just the change.
labelNoWhat to call this session, up to 60 characters. Shown as who did it.
modelNoFor claim and ship: the model the agent runs on, like claude-opus-5-5. Shown beside its name.
shipsNoFor escalate: true when the ask is 'ship this PR'. Needs pr_url.
topicNoFor escalate: what the ask is about, in a few words.
whereNoFor verify: a test id (path::test) or a URL that shows the check.
actionYesship: Mark the priority shipped. It only records it; nothing deploys. retract undoes it. claim: Take a priority to work on. Starts a spec if there isn't one and gives you spec_id and holder_key. note: Leave a note on the spec about what you did or found. To correct an earlier note, send a new one with supersedes. handoff: Pass the work to another agent or a person, with a note for them. dispatch: Post @claude on the priority's GitHub issue so Claude picks it up there. The person stays assigned. A person's action. unclaim: Unclaim a priority so another agent can pick it up. close: Close the priority in one call, even if it's claimed or has a PR. It stays under Closed with your reason. write: Replace one section of the spec with new text. If the section belongs to someone else, your text is saved as a proposed change for them. verify: Record how you checked one Done When line, by proof kind: a test id for (proof: test), a URL for staging or prod. It doesn't block ship. escalate: Ask a person to decide something; it lands in their Needs you. Send topic, ask, trigger, principle and checked. One open ask per priority; the same topic updates it. resolve: Settle a routine question, like 'is this a duplicate of #N?', the way your principles already decide it. Each outcome fits one kind of question. Returns use_id so you can undo. undo: Reverse your own resolve, by use_id.
pr_urlNoThe GitHub PR link. Its body carries 'Annsa-Spec: <spec id>'.
reasonNoWhy, in a line. Needed for takeover, close, unclaim, handoff, and a park or retract request.
use_idNoFor undo: the id resolve gave you.
checkedNoFor escalate: what you checked before asking, as 'what — result'.
learnedNoFor ship or escalate: what the next agent should know.
optionsNoFor escalate: the choices, as short labels.
outcomeNoFor resolve: keep_both (a merge ask), close_settled, dismiss_came_back or move_row (a stray row). Each fits one kind of ask.
purposeNoFor escalate: decision (pick between options), help (needs a person's hand), gap (something missing) or update (just telling).
requestNoFor escalate: park or retract, to ask the person for one. Needs reason.
sectionNoFor write: the_problem, evidence_and_direction, what_to_build, files_to_touch or done_when. For note: build, how_it_works or spec.
spec_idNoThe spec id from claim, or build_id from annsa.spec. Required for verify.
triggerNoFor escalate: why this needs a person: scope, customers, principle or options. Anything else is settled, not raised.
verdictNoFor unclaim: false_positive marks the finding wrong. still_broken and fixed belong to annsa.file submit.
securityNoFor escalate: true if this is a security question.
takeoverNoClaim or unclaim work someone else holds. Needs reason. Another session of your own counts as someone else.
principleNoFor escalate: the rule that would let an agent settle this kind of question next time.
recommendNoFor a decision: the option you would take.
ruled_outNoOptions you ruled out, one per entry as 'option — why'.
holder_keyNoFrom claim; send it on write and ship.
supersedesNoFor note: the note this replaces. For principle: the principle this replaces.
assigned_toNoWho gets it: an agent (like claude-code or codex) or a person's email. Empty unassigns.
next_actionNoFor note or handoff: what should happen next on this priority.
priority_idNoThe long id, instead of priority_number.
feedback_idsNoFor resolve: the rows the ask is about.
quiet_minutesNoFor note: how long you expect to be quiet, in minutes.
include_memoryNoFor claim: add related answers and what earlier work learned.
done_when_indexNoFor verify: which Done When line, counting from 1 as annsa.spec lists them.
priority_numberNoThe # number, e.g. 20 for #20.
include_principlesNoFor claim: add the full text of the principles that apply.
same_as_priority_numberNoFor escalate: the priority this looks like a duplicate of; a person decides the merge.

Output Schema

NameRequiredDescription
whoNo
recordNo
messageNo
successNo

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 8 tool updates
    • Changedannsa_ask11 fields changed
      • addedInput schema / properties / about / description
        Added value: +"Where to look: feedback (default), annsa (the docs), surveys, customer, accounts, templates or transcript."
      • changedInput schema / properties / account / description
        Previous value: -"Narrows `customer` to one company"New value: +"With customer: which company, if the name matches more than one."
      • changedInput schema / properties / customer / description
        Previous value: -"With about='customer': a name, email or id"New value: +"With about=customer: their name, email or id."
      • changedInput schema / properties / do_we_have / description
        Previous value: -"The text you are about to file; returns the nearest priorities"New value: +"The text you're about to file. Returns the nearest priorities, each judged same, possibly or different."
      • changedInput schema / properties / from / description
        Previous value: -"With do_we_have: a customer's words or an agent's finding"New value: +"With do_we_have: customer (a customer's words) or agent (an agent's finding)."
      • changedInput schema / properties / have_version / description
        Previous value: -"The version of your saved copy of the file"New value: +"With skill: the version of the copy you already have, so you only get it if it changed."
      • addedInput schema / properties / page / description
        Added value: +"For a long transcript: which page, starting at 1."
      • addedInput schema / properties / question / description
        Added value: +"What you want to know, in a sentence."
      • changedInput schema / properties / skill / description
        Previous value: -"Returns a skill file instead of an answer; no question needed"New value: +"Returns a skill file instead of an answer: working, spec-skill, decisions or welcome. No question needed."
      • changedInput schema / properties / transcript / description
        Previous value: -"t12 or its id; long ones come in pages"New value: +"With about=transcript: which call, like t12 or its id. Long ones come in pages."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
    • Changedannsa_board47 fields changed
      • changedInput schema / properties / action / description
        Previous value: -"set_stage: Sets the planning stage. correct: Fixes a title, detail or ruled-out entry, keeping the old version. retract: Unfiles feedback and marks a ship not shipped. regroup: Moves priorities between groups; the reply carries the undo. merge: Folds duplicates into `into`; their numbers are retired. Refuses shipped priorities. bet: Manages bets and places priorities on them. cut: Closes a release and writes its changelog. pick: Sets a person's short list. approve_findings: Lets through agent findings held back by the daily limit; the owner's. view: Saves a board view; an agent's is a suggestion."New value: +"set_stage: Move a priority to open, ready or closed. assign: Set who a spec is assigned to. A person's action. correct: Fix a title, detail or ruled-out entry. The old wording is kept. park: Take a priority off the list, with a reason, until someone unparks it. A person's action. unpark: Put a parked priority back on the list. retract: Unfile feedback, or mark a shipped priority as not shipped. A person's action; without confirm it only shows the plan. regroup: Move priorities between groups; the reply carries the undo. merge: Fold duplicate priorities into one. Their numbers are retired for good. Shipped priorities can't be merged. bet: List, create, update, delete or reorder bets, or place priorities on one. op says which. direction: Read, list, update or comment on a Direction page. op says which. set_severity: Set a priority's severity, P0 to P3. From an agent it's a proposal and needs a reason; a person's typed severity wins. cut: Close a release and write its changelog. op=publish marks its rows Shared. pick: Set a person's short list of priorities, in order. approve_findings: Let through agent findings held back by the daily limit. The owner's action. view: Save a board view. An agent's is a suggestion until a person keeps or dismisses it."
      • changedInput schema / properties / aim_pct / description
        Previous value: -"How much of your effort this bet should get, 0 to 100."New value: +"For a bet: how much of your effort it should get, 0 to 100."
      • changedInput schema / properties / allow_shared / description
        Previous value: -"Retract is refused once customers were told, unless true"New value: +"For retract: true to retract even after customers were told."
      • changedInput schema / properties / assigned_to / description
        Previous value: -"An agent client or a member's email; empty unassigns"New value: +"Who gets it: an agent (like claude-code or codex) or a person's email. Empty unassigns."
      • addedInput schema / properties / at / description
        Added value: +"For cut: the release date."
      • addedInput schema / properties / bet_id / description
        Added value: +"For bet update, delete or place: which bet."
      • changedInput schema / properties / bucket / description
        Previous value: -"The group this bet counts toward, like Product or GTM."New value: +"For a bet: the group it counts toward, like Product or GTM."
      • changedInput schema / properties / channel / description
        Previous value: -"For cut op=publish."New value: +"For cut op=publish: changelog or marketing."
      • addedInput schema / properties / comment / description
        Added value: +"For direction op=comment: your words."
      • changedInput schema / properties / confirm / description
        Previous value: -"Without it retract only shows the plan"New value: +"For retract: true to do it. Without it the reply only shows what would change."
      • changedInput schema / properties / corrected / description
        Previous value: -"What it should say now."New value: +"For correct: what it should say now."
      • changedInput schema / properties / correction_type / description
        Previous value: -"'category' is a person's; the old wording is kept"New value: +"For correct: 'title', 'detail', 'ruled_out' or 'category'. 'category' is a person's; the old wording is kept."
      • addedInput schema / properties / document_id / description
        Added value: +"For direction approve or dismiss: which page."
      • changedInput schema / properties / document_text / description
        Previous value: -"At least 50 characters"New value: +"For direction update: the page text, at least 50 characters."
      • addedInput schema / properties / duplicates / description
        Added value: +"For merge: the priorities being folded into `into`."
      • addedInput schema / properties / evidence / description
        Added value: +"For direction op=update: the evidence behind the change."
      • changedInput schema / properties / expected_stage / description
        Previous value: -"Only change it if the stage is still this."New value: +"For set_stage: only change it if the stage is still this: open, ready or closed."
      • addedInput schema / properties / feedback_ids / description
        Added value: +"For retract: the feedback rows to unfile."
      • addedInput schema / properties / into / description
        Added value: +"For merge: the priority that stays."
      • changedInput schema / properties / items / description
        Previous value: -"For regroup: the new area for each priority."New value: +"For regroup: the new group for each priority."
      • addedInput schema / properties / label / description
        Added value: +"What to call this session, up to 60 characters. Shown as who did it."
      • addedInput schema / properties / metric_label / description
        Added value: +"For a new bet: what the measure is called."
      • changedInput schema / properties / metric_value / description
        Previous value: -"For a written bet: the number now (a person's)."New value: +"For a written bet: the number now. A person's."
      • changedInput schema / properties / op / description
        Previous value: -"For action 'bet': 'list', 'create' (title + metric_label; last for agents), 'update' (bet_id), 'delete', 'reorder', 'place' (priority_ids). For action 'direction': 'get', 'list', 'update' (document_text + reason), 'comment' (thread_id replies), 'approve' and 'dismiss' (document_id + reason; a person's). For action 'cut': publish takes release_number, channel and the live annsa.ai url; it marks the release's rows Shared and sends nothing. For action 'view': 'keep' and 'dismiss' are a person's."New value: +"For bet: 'list', 'create' (title and metric_label; agents last), 'update' (bet_id), 'delete', 'reorder' (bet_ids) or 'place' (priority_ids). For direction: 'get', 'list', 'update' (document_text and reason), 'comment' (thread_id), or 'approve' and 'dismiss' (document_id and reason; a person's). For cut: 'publish', with release_number, channel and the live annsa.ai url. It marks the release's rows Shared and sends nothing. For view: 'list', 'create', 'update', 'delete', or 'keep' and 'dismiss' (a person's)."
      • changedInput schema / properties / original / description
        Previous value: -"For a category fix, the old category; for a ruled-out fix, the entry being replaced."New value: +"For correct: the old category, or the ruled-out entry being replaced."
      • changedInput schema / properties / owner_user_id / description
        Previous value: -"'none' clears the owner"New value: +"For bet update: the owner's user id; none clears it."
      • addedInput schema / properties / parent / description
        Added value: +"The priority this one sits under. For bet op=place: the bet."
      • changedInput schema / properties / park_reason / description
        Previous value: -"Why it's parked (required, up to 500 characters)."New value: +"For park: why, up to 500 characters."
      • changedInput schema / properties / person / description
        Previous value: -"Email or user id of the member whose words they are"New value: +"The email or user id of the person whose words they are."
      • changedInput schema / properties / person_words / description
        Previous value: -"The person's exact words, not a summary; recorded as their quote"New value: +"The person's exact words, not a summary. Recorded as their quote."
      • addedInput schema / properties / priority_ids / description
        Added value: +"For bet op=place or direction: the priorities."
      • addedInput schema / properties / question / description
        Added value: +"For view: the question the saved view answers."
      • addedInput schema / properties / quote / description
        Added value: +"For direction op=comment: the line you're replying to."
      • changedInput schema / properties / reason / description
        Previous value: -"Required for takeover, release, retract, correct and an agent's severity"New value: +"Why, in a line. Needed for retract, correct, merge and an agent's severity."
      • changedInput schema / properties / recipe / description
        Previous value: -"annsa.priorities args"New value: +"For view: the annsa.priorities arguments the view runs."
      • addedInput schema / properties / release_number / description
        Added value: +"For cut op=publish: which release."
      • changedInput schema / properties / severity / description
        Previous value: -"0 broken, 1 poor, 2 could be better, 3 minor. From an agent: a proposal until a person types the P."New value: +"0 broken, 1 poor, 2 could be better, 3 minor. From an agent it's a proposal until a person sets it."
      • addedInput schema / properties / since / description
        Added value: +"For cut: the start of the window the release covers."
      • changedInput schema / properties / spec_id / description
        Previous value: -"The spec id from claim or annsa.spec (build_…)."New value: +"For assign and retract: the spec id."
      • addedInput schema / properties / stage / description
        Added value: +"For set_stage: open, ready or closed."
      • addedInput schema / properties / thread_id / description
        Added value: +"For direction op=comment: the thread to reply in."
      • addedInput schema / properties / title / description
        Added value: +"For bet or view: its title."
      • addedInput schema / properties / until / description
        Added value: +"For cut: the end of that window."
      • addedInput schema / properties / url / description
        Added value: +"For cut op=publish: the live changelog link."
      • changedInput schema / properties / view_id / description
        Previous value: -"The saved view to update or delete, from view op=list."New value: +"For view update or delete: which view, from view op=list."
      • changedInput schema / properties / why_now / description
        Previous value: -"Why this bet matters now, in a line."New value: +"For a bet: why it matters now, in a line."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
    • Changedannsa_decide30 fields changed
      • changedInput schema / properties / action / description
        Previous value: -"approve: Writes another writer's proposed section text. dismiss: Keeps the current section text. answer: Records a person's answer, typed or relayed with person_words; an option that names an act runs it. direct: A person steers the agent holding a priority; it reads the words on its next reply, once. choose: Records a person's pick on a Needs you question: one option, or neither. sign: Records a person's decision. principle: Decision memory; propose applies at once."New value: +"approve: Accept another writer's proposed section text, by update_id. dismiss: Turn down a proposed section text; the current text stays. answer: Record a person's answer to the open ask on a priority. An agent passes on the person's exact words with person_words. Picking an option labelled Merge, Ship it, Park it or Retract the ship runs it; free text is only recorded. ask_back: A person asks the agent a question back on a priority. A person's action. direct: A person gives the agent holding a priority a direction; the agent reads it on its next reply. A person's action. choose: Record a person's pick on a Needs you question (send disagreement_id). One option, or neither. A person's action. sign: Record a person's decision on a priority (do_this, do_nothing, park or dismiss), with because. A person's action. principle: Your decision memory. Agents can list principles or propose one; a person writes, retires or reactivates them. A proposal applies at once."
      • addedInput schema / properties / answer / description
        Added value: +"For choose: the option picked, or neither. For principle: the answer behind the rule."
      • addedInput schema / properties / answered_by / description
        Added value: +"The person who decided, when you're passing on their words."
      • addedInput schema / properties / area / description
        Added value: +"For scope=area: the part of the product the rule covers."
      • addedInput schema / properties / because / description
        Added value: +"For sign: why, in a sentence."
      • addedInput schema / properties / decision / description
        Added value: +"For sign: do_this, do_nothing, park or dismiss."
      • changedInput schema / properties / decision_until / description
        Previous value: -"YYYY-MM-DD"New value: +"For sign: when this decision expires, like 2026-12-31."
      • changedInput schema / properties / disagreement_id / description
        Previous value: -"The id of the Needs you question being answered, from the Needs you list."New value: +"For choose: the id of the Needs you question, from the Needs you list."
      • changedInput schema / properties / falsifier_due / description
        Previous value: -"YYYY-MM-DD: when to check wrong_if"New value: +"For sign: when to check wrong_if, like 2026-12-31."
      • addedInput schema / properties / label / description
        Added value: +"What to call this session, up to 60 characters. Shown as who did it."
      • changedInput schema / properties / may_decide / description
        Previous value: -"Needs answered_by"New value: +"For sign: what the agent may decide on its own from here. Needs answered_by."
      • addedInput schema / properties / must_come_back / description
        Added value: +"For sign: what the agent has to bring back to a person."
      • changedInput schema / properties / op / description
        Previous value: -"For action 'principle': 'propose' (an agent's), 'write', 'retire', 'activate' (a person's), 'list'."New value: +"For principle: 'list', 'propose' (an agent's), or 'write', 'retire' and 'activate' (a person's)."
      • addedInput schema / properties / option / description
        Added value: +"For answer: the option's label."
      • changedInput schema / properties / person / description
        Previous value: -"Email or user id of the member whose words they are"New value: +"The email or user id of the person whose words they are."
      • changedInput schema / properties / person_words / description
        Previous value: -"The person's exact words, not a summary; recorded as their quote"New value: +"The person's exact words, not a summary. Recorded as their quote."
      • changedInput schema / properties / principle / description
        Previous value: -"The rule that would settle this class next time"New value: +"For principle: the rule, in a sentence."
      • changedInput schema / properties / principle_id / description
        Previous value: -"The principle to retire or activate, from principle op=list."New value: +"For principle retire or activate: which one, from principle op=list."
      • changedInput schema / properties / review_condition / description
        Previous value: -"When to look at this decision again, in a sentence."New value: +"For sign: when to look at this decision again, in a sentence."
      • changedInput schema / properties / ruled_out / description
        Previous value: -"One 'label — why' per entry"New value: +"Options you ruled out, one per entry as 'option — why'."
      • changedInput schema / properties / scope / description
        Previous value: -"area needs `area`; area or company also writes a principle"New value: +"How far the decision reaches: priority, area (needs area) or company. area or company also writes a principle."
      • changedInput schema / properties / supersedes / description
        Previous value: -"The note or principle this replaces."New value: +"For principle: the principle this replaces."
      • changedInput schema / properties / take / description
        Previous value: -"For do_this: the option you chose, in a few words (up to 200 characters)."New value: +"For sign with do_this: the option you chose, in a few words."
      • addedInput schema / properties / text / description
        Added value: +"For direct or ask_back: the words."
      • addedInput schema / properties / title / description
        Added value: +"For principle: the rule's title."
      • addedInput schema / properties / topic / description
        Added value: +"For principle: what the rule is about."
      • changedInput schema / properties / update_id / description
        Previous value: -"The proposed change to approve or dismiss, from annsa.spec's updates."New value: +"For approve or dismiss: the proposed change, from annsa.spec's updates."
      • changedInput schema / properties / while_waiting / description
        Previous value: -"What the agent may keep doing until the answer comes."New value: +"For sign: what the agent may keep doing until the answer comes."
      • addedInput schema / properties / wrong_if / description
        Added value: +"For sign: what would show the decision was wrong."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
    • Changedannsa_file38 fields changed
      • changedInput schema / properties / action / description
        Previous value: -"submit: Adds one feedback row; an agent's is a finding. With priority_number it attaches there; with stand_alone it proposes a new priority. report: Tell the Annsa team about a bug, gap or idea in Annsa. Needs `text`; `title` names the tool and action. The Annsa team reads it, so keep your customers' data out. add_page: Makes a page from a template, private to you; returns its link. add_template: Saves a template (title, text, when_to_use), private to you; {blanks} are its fields. connect_goal: Answer the welcome's optional question: what the person wants from Annsa, up to 300 characters. Goes to the Annsa team, not your board. import_direction: Two steps: preview a strategy doc's lines, then add the ones you pick as ideas. add_priority: Adds a priority from a title and detail, with no customer words."New value: +"submit: File what a customer said or what you found. With priority_number it attaches to that priority; with stand_alone it starts a new one. report: Tell the Annsa team about a bug, gap or idea in Annsa itself. Send text; title names the tool and action. Keep your customers' data out of it. add_page: Make a page from a template, private to you. Returns the link. add_template: Save a template with a title, text and when to use it. {blanks} in the text become its fields. connect_goal: Answer the welcome's optional question about what you want from Annsa, up to 300 characters. Goes to the Annsa team, not your board. add_transcript: Add a call transcript as customer feedback. What the customer asked for is filed from it. A person's action. import_direction: Import a strategy doc in two steps. First preview its lines, then add the ones you pick as ideas. A person's action. add_priority: Add a priority from a title and detail, with no customer words."
      • changedInput schema / properties / adjudicated / description
        Previous value: -"Raw scanner output is refused unless someone checked it"New value: +"True if a person checked this scanner finding; raw scanner output is refused."
      • changedInput schema / properties / call_type / description
        Previous value: -"For add_transcript (default other)."New value: +"For add_transcript: interview, sales_call, support or other (the default)."
      • addedInput schema / properties / customer_email / description
        Added value: +"Their email, if you have it."
      • addedInput schema / properties / customer_name / description
        Added value: +"The customer who said it."
      • changedInput schema / properties / detail / description
        Previous value: -"The longer words of the row, up to 20000 characters"New value: +"For add_priority: the longer words of the row, up to 20000 characters."
      • changedInput schema / properties / doc_id / description
        Previous value: -"The Direction page to save into; leave it out for a new page."New value: +"Which Direction page. Leave it out for a new page, or the Overview."
      • changedInput schema / properties / doc_title / description
        Previous value: -"The page's title (kept if you send none)."New value: +"The page's title. Kept if you send none."
      • changedInput schema / properties / document_text / description
        Previous value: -"At least 50 characters"New value: +"For import_direction: the document, at least 50 characters."
      • changedInput schema / properties / feedback / description
        Previous value: -"The words, verbatim"New value: +"For submit: what was said, word for word."
      • addedInput schema / properties / fields / description
        Added value: +"For add_page: a value for each {blank} in the template."
      • changedInput schema / properties / from / description
        Previous value: -"Who said it"New value: +"Who said it: customer, team, agent, idea or roadmap."
      • changedInput schema / properties / insist / description
        Previous value: -"Files it without the check for a matching priority."New value: +"For submit and add_priority: file it even if a matching priority exists."
      • addedInput schema / properties / label / description
        Added value: +"What to call this session, up to 60 characters. Shown as who did it."
      • addedInput schema / properties / line / description
        Added value: +"For submit from a scanner: the line number."
      • changedInput schema / properties / origin_ref / description
        Previous value: -"Where it came from, like a ticket or file:line; the same one again adds to the same row."New value: +"Where it came from, like a ticket or file:line. The same one again adds to the same row."
      • addedInput schema / properties / parent / description
        Added value: +"The priority this one sits under. For bet op=place: the bet."
      • addedInput schema / properties / path / description
        Added value: +"For submit from a scanner: the file."
      • changedInput schema / properties / proposal_id / description
        Previous value: -"For import_direction: the id phase 1 returned, to land phase 2"New value: +"For import_direction: the id the preview returned, to add the lines you picked."
      • changedInput schema / properties / reason / description
        Previous value: -"Required for takeover, release, retract, correct and an agent's severity"New value: +"For add_priority: why you're filing it, in a line."
      • changedInput schema / properties / reference / description
        Previous value: -"A followable link (PR, URL, log line); findings need one"New value: +"A link someone can follow: a PR, URL or log line. A finding needs one."
      • changedInput schema / properties / revenue_band / description
        Previous value: -"An amount ('499') or a tier word"New value: +"What the customer pays: an amount like 499, or a tier word."
      • changedInput schema / properties / root_cause / description
        Previous value: -"When ___, ___ can't ___ because ___; sent on the submit. Max 300 characters"New value: +"The cause in one line, shaped 'When ___, ___ can't ___ because ___'. Up to 300 characters."
      • addedInput schema / properties / rule / description
        Added value: +"For submit from a scanner: the rule that fired."
      • changedInput schema / properties / selection / description
        Previous value: -"Titles to land in phase 2; omitted lands all"New value: +"For import_direction: which lines to add, by title. Leave it out to add all."
      • changedInput schema / properties / severity / description
        Previous value: -"0 broken, 1 poor, 2 could be better, 3 minor. From an agent: a proposal until a person types the P."New value: +"0 broken, 1 poor, 2 could be better, 3 minor. From an agent it's a proposal until a person sets it."
      • changedInput schema / properties / severity_reason / description
        Previous value: -"Why this P; sent on the submit with severity"New value: +"Why this severity, in a line."
      • changedInput schema / properties / source / description
        Previous value: -"Where the feedback came from, like intercom."New value: +"Where the feedback came from, like intercom. Defaults to mcp."
      • changedInput schema / properties / stand_alone / description
        Previous value: -"Makes a new priority from this row; not with priority_number."New value: +"For submit: start a new priority from this row. Not with priority_number."
      • addedInput schema / properties / template / description
        Added value: +"For add_page: the template's key, from annsa.ask about=templates."
      • addedInput schema / properties / text / description
        Added value: +"For report, add_template, connect_goal and add_transcript: the words. submit takes feedback."
      • changedInput schema / properties / theme / description
        Previous value: -"One of the workspace's themes"New value: +"The group it belongs to, one of the workspace's themes."
      • addedInput schema / properties / title / description
        Added value: +"For add_priority, add_page, add_template or report: the title."
      • changedInput schema / properties / type / description
        Previous value: -"What kind of row it is."New value: +"Which kind: bug, feature, improvement, praise or question."
      • changedInput schema / properties / verdict / description
        Previous value: -"On a shipped priority: still_broken or fixed. On release, false_positive does NOT close the row."New value: +"For submit on a shipped priority: still_broken or fixed. false_positive doesn't close the row."
      • addedInput schema / properties / when_to_use / description
        Added value: +"For add_template: when an agent should pick this template."
      • changedInput schema / properties / with_spec / description
        Previous value: -"Also writes a ready spec and returns its spec_id."New value: +"For submit and add_priority: also write a ready spec and return its spec_id."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
    • Changedannsa_priorities19 fields changed
      • changedInput schema / properties / bet / description
        Previous value: -"A bet id, or 'unplaced' for the proposal inbox"New value: +"Only priorities on this bet, by id. unplaced lists the ones no bet has yet."
      • changedInput schema / properties / include / description
        Previous value: -"Long lists, comma separated: agents, to_verify, in_build, unrated_filings or all."New value: +"Extra lists to include, comma separated: agents, to_verify, in_build, unrated_filings or all."
      • addedInput schema / properties / include_parked / description
        Added value: +"Include parked priorities too."
      • 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 100"New value: +"How many to return. Defaults to 5, max 100."
      • changedInput schema / properties / mine / description
        Previous value: -"Only the priorities you hold; the reply carries `needs_me`."New value: +"Only the priorities you're working on. The reply also counts what needs you."
      • addedInput schema / properties / person / description
        Added value: +"A person's email. With picked, whose picked list."
      • changedInput schema / properties / picked / description
        Previous value: -"A person's picked list; `person` says whose"New value: +"Only the priorities a person picked; person says whose."
      • removedInput schema / properties / rank_by / default
        Removed value: -"volume"
      • changedInput schema / properties / rank_by / description
        Previous value: -"retention is unhappy customers, delight is praise, feature is new-feature asks."New value: +"Leave it out for the board's order, the same as the app. Or rank by volume, urgency, revenue, retention (unhappy customers), delight (praise) or feature (new-feature asks)."
      • addedInput schema / properties / release_number / description
        Added value: +"Only the priorities in this release."
      • changedInput schema / properties / segment / description
        Previous value: -"enterprise or smb"New value: +"Customer size: all (default), enterprise or smb."
      • changedInput schema / properties / stage / description
        Previous value: -"Default: the ranked active priorities (open, ready, building)."New value: +"open, ready, building, shipped, shared or closed. Leave it out for the ranked active priorities: open, ready and building."
      • changedInput schema / properties / topic / description
        Previous value: -"Matches a priority's wording and its feedback"New value: +"A word or phrase to search for in priorities and their feedback."
      • addedInput schema / properties / type / description
        Added value: +"Only this kind: bug, feature, improvement, praise or question."
      • changedInput schema / properties / view / description
        Previous value: -"radar, brief or a saved view"New value: +"A saved view by name, or radar (what's rising, shipped and quiet) or brief."
      • addedInput schema / properties / weekly / description
        Added value: +"A summary of the week instead of the list: what's rising, what shipped, what went quiet."
      • changedInput schema / properties / window / description
        Previous value: -"How far back the radar looks."New value: +"How far back the radar looks: 7d, 14d or 30d. Defaults to 7d."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
    • Changedannsa_share6 fields changed
      • changedInput schema / properties / action / description
        Previous value: -"share: Emails or notifies the customers who asked that it shipped. An email cannot be unsent."New value: +"share: Email or notify the customers who asked that it shipped. An email cannot be unsent."
      • changedInput schema / properties / channel / description
        Previous value: -"Who to tell: widget is in the app; both is the default; skip tells nobody."New value: +"Who to tell: email, widget (in the app), both (the default) or skip (nobody)."
      • addedInput schema / properties / label / description
        Added value: +"What to call this session, up to 60 characters. Shown as who did it."
      • changedInput schema / properties / message / description
        Previous value: -"Your own words, instead of the default note."New value: +"For share: your own words, instead of the default note."
      • changedInput schema / properties / spec_id / description
        Previous value: -"The spec id from claim or annsa.spec (build_…)."New value: +"The shipped spec, by id."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
    • Changedannsa_spec16 fields changed
      • 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"
        +}
    • Changedannsa_work36 fields changed
      • changedInput schema / properties / action / description
        Previous value: -"ship: Records completion and deploys nothing; retract undoes it. claim: Claims the priority, starts a short spec and returns holder_key. note: Appends a note; a correction is a new note with supersedes. dispatch: Posts @claude on the priority's linked GitHub issue; the person stays assigned. unclaim: Puts the work down; nothing is marked shipped. close: Closes a priority in one call, claim or PR and all; it stays under Closed. write: Replaces one spec section as a new version; text for a section that is not yours is recorded as an update. verify: Records how a line was checked, by proof kind. No ship gate. escalate: Raises a three-line ask in a person's Needs you; decides nothing. Needs `checked`: a fact you can check is not asked. One open ask per priority; the same topic updates it. resolve: Answers a routine ask the way your principles already decide it; returns use_id for undo. undo: Puts back your own resolve by use_id."New value: +"ship: Mark the priority shipped. It only records it; nothing deploys. retract undoes it. claim: Take a priority to work on. Starts a spec if there isn't one and gives you spec_id and holder_key. note: Leave a note on the spec about what you did or found. To correct an earlier note, send a new one with supersedes. handoff: Pass the work to another agent or a person, with a note for them. dispatch: Post @claude on the priority's GitHub issue so Claude picks it up there. The person stays assigned. A person's action. unclaim: Unclaim a priority so another agent can pick it up. close: Close the priority in one call, even if it's claimed or has a PR. It stays under Closed with your reason. write: Replace one section of the spec with new text. If the section belongs to someone else, your text is saved as a proposed change for them. verify: Record how you checked one Done When line, by proof kind: a test id for (proof: test), a URL for staging or prod. It doesn't block ship. escalate: Ask a person to decide something; it lands in their Needs you. Send topic, ask, trigger, principle and checked. One open ask per priority; the same topic updates it. resolve: Settle a routine question, like 'is this a duplicate of #N?', the way your principles already decide it. Each outcome fits one kind of question. Returns use_id so you can undo. undo: Reverse your own resolve, by use_id."
      • addedInput schema / properties / ask / description
        Added value: +"For escalate: the question you want the person to answer, in one line."
      • changedInput schema / properties / assigned_to / description
        Previous value: -"An agent client or a member's email; empty unassigns"New value: +"Who gets it: an agent (like claude-code or codex) or a person's email. Empty unassigns."
      • changedInput schema / properties / checked / description
        Previous value: -"What you checked before asking, as \"what — result\"."New value: +"For escalate: what you checked before asking, as 'what — result'."
      • changedInput schema / properties / done_when_index / description
        Previous value: -"Which Done When line, counting from 1 as annsa.spec does."New value: +"For verify: which Done When line, counting from 1 as annsa.spec lists them."
      • addedInput schema / properties / feedback_ids / description
        Added value: +"For resolve: the rows the ask is about."
      • addedInput schema / properties / how / description
        Added value: +"For verify: how you checked the line: test, staging, prod or manual."
      • changedInput schema / properties / include_memory / description
        Previous value: -"claim: adds related_answers, learned"New value: +"For claim: add related answers and what earlier work learned."
      • changedInput schema / properties / include_principles / description
        Previous value: -"claim: the rules in full"New value: +"For claim: add the full text of the principles that apply."
      • addedInput schema / properties / into / description
        Added value: +"For resolve move_row: the priority the row moves to."
      • addedInput schema / properties / label / description
        Added value: +"What to call this session, up to 60 characters. Shown as who did it."
      • addedInput schema / properties / learned / description
        Added value: +"For ship or escalate: what the next agent should know."
      • addedInput schema / properties / model
        Added value: +{
        +  "description": "For claim and ship: the model the agent runs on, like claude-opus-5-5. Shown beside its name.",
        +  "type": "string"
        +}
      • changedInput schema / properties / next_action / description
        Previous value: -"What should happen next on this priority."New value: +"For note or handoff: what should happen next on this priority."
      • changedInput schema / properties / options / description
        Previous value: -"Short labels, for a decision"New value: +"For escalate: the choices, as short labels."
      • addedInput schema / properties / outcome / description
        Added value: +"For resolve: keep_both (a merge ask), close_settled, dismiss_came_back or move_row (a stray row). Each fits one kind of ask."
      • changedInput schema / properties / pr_url / description
        Previous value: -"GitHub PR URL; body has 'Annsa-Spec: <spec id>'"New value: +"The GitHub PR link. Its body carries 'Annsa-Spec: <spec id>'."
      • changedInput schema / properties / principle / description
        Previous value: -"The rule that would settle this class next time"New value: +"For escalate: the rule that would let an agent settle this kind of question next time."
      • changedInput schema / properties / purpose / description
        Previous value: -"For escalate: decision picks between options, help needs a person's hand, gap is something missing, update is just telling."New value: +"For escalate: decision (pick between options), help (needs a person's hand), gap (something missing) or update (just telling)."
      • changedInput schema / properties / quiet_minutes / description
        Previous value: -"On a note: how long you expect to be quiet, in minutes."New value: +"For note: how long you expect to be quiet, in minutes."
      • changedInput schema / properties / reason / description
        Previous value: -"Required for takeover, release, retract, correct and an agent's severity"New value: +"Why, in a line. Needed for takeover, close, unclaim, handoff, and a park or retract request."
      • changedInput schema / properties / request / description
        Previous value: -"Needs reason; a person decides."New value: +"For escalate: park or retract, to ask the person for one. Needs reason."
      • changedInput schema / properties / ruled_out / description
        Previous value: -"One 'label — why' per entry"New value: +"Options you ruled out, one per entry as 'option — why'."
      • changedInput schema / properties / same_as_priority_number / description
        Previous value: -"Proposes a merge for a person to answer"New value: +"For escalate: the priority this looks like a duplicate of; a person decides the merge."
      • changedInput schema / properties / section / description
        Previous value: -"The spec section: the_problem, evidence_and_direction, what_to_build, files_to_touch or done_when. On a note: build, how_it_works or spec."New value: +"For write: the_problem, evidence_and_direction, what_to_build, files_to_touch or done_when. For note: build, how_it_works or spec."
      • changedInput schema / properties / security / description
        Previous value: -"True for a security question"New value: +"For escalate: true if this is a security question."
      • changedInput schema / properties / ships / description
        Previous value: -"True when the ask is \"ship this PR\"; needs pr_url."New value: +"For escalate: true when the ask is 'ship this PR'. Needs pr_url."
      • changedInput schema / properties / spec_id / description
        Previous value: -"The spec id from claim or annsa.spec (build_…). Required for verify."New value: +"The spec id from claim, or build_id from annsa.spec. Required for verify."
      • changedInput schema / properties / supersedes / description
        Previous value: -"The note or principle this replaces."New value: +"For note: the note this replaces. For principle: the principle this replaces."
      • changedInput schema / properties / takeover / description
        Previous value: -"Another session of your own client counts as someone else; needs a reason"New value: +"Claim or unclaim work someone else holds. Needs reason. Another session of your own counts as someone else."
      • addedInput schema / properties / topic / description
        Added value: +"For escalate: what the ask is about, in a few words."
      • changedInput schema / properties / trigger / description
        Previous value: -"Anything else is settled, not raised."New value: +"For escalate: why this needs a person: scope, customers, principle or options. Anything else is settled, not raised."
      • addedInput schema / properties / use_id / description
        Added value: +"For undo: the id resolve gave you."
      • changedInput schema / properties / verdict / description
        Previous value: -"On a shipped priority: still_broken or fixed. On release, false_positive does NOT close the row."New value: +"For unclaim: false_positive marks the finding wrong. still_broken and fixed belong to annsa.file submit."
      • changedInput schema / properties / where / description
        Previous value: -"A test id (path::test) or a URL that shows the check."New value: +"For verify: a test id (path::test) or a URL that shows the check."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "properties": {
        +    "message": {
        +      "type": "string"
        +    },
        +    "record": {
        +      "type": "object"
        +    },
        +    "success": {
        +      "type": "boolean"
        +    },
        +    "who": {
        +      "type": "object"
        +    }
        +  },
        +  "type": "object"
        +}
  2. 8 tool updates
    • First observedannsa_ask
    • First observedannsa_board
    • First observedannsa_decide
    • First observedannsa_file
    • First observedannsa_priorities
    • First observedannsa_share
    • First observedannsa_spec
    • First observedannsa_work

Publisher details

Operator
Annsa (Circuit Software Pty Ltd) · Publisher source
Vendor relationship
First-party · Publisher source
Restrictions
Requires an Annsa account (public sign-up at annsa.ai). Sign-in is OAuth. Free trial, then paid plans per person per month. No admin approval or regional limits. · Publisher source

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Gives AI coding agents native tools to pull their next prioritized, unblocked task with a full briefing (description, acceptance criteria, context files, conventions), comment and tick off criteria with evidence, ask the human decision-maker questions, and submit structured handoffs for review. It lets agents plan epics and sprints, report checks, create new tasks, and release work with checkpoints — all against a self-hosted board rather than files in the repo.
    6 npm
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources