Planner (proof-of-done)

goal-update

Idempotent

Partial update of a goal — only the fields you pass are changed; omitted fields are untouched. Updatable: title, status, priority (1-5), description, type, tags, deadline, estimate, mode, attemptCommit (git SHA of the attempt commit; once a deployed revision contains it, post-deploy probes of this goal run automatically and record machine verdicts — pass "" to clear), dismissVisualAcSuggestion. Status transitions follow a matrix: backlog→ready_for_work (author; grove: requires ≥1 AC, red-team check when the project requires it — the goal parks in checking_ac and becomes ready_for_work, checking_ac_failed (hole in AC set) or checking_ac_errored (check did not run)); ready_for_work|checking_ac_errored→in_progress (executor, no checks); in_progress→done (file-evidence on every AC + session_history) | blocked | cancelled. A visible-UI goal with an outstanding visualAcSuggestion returns an advisory before ready_for_work freezes the AC contract: accept it through goal-add-criterion(visualEvidenceSuggested=true), or retry this same update with dismissVisualAcSuggestion=true. The first MCP dismissal persists the choice and notifies Product Events with the goal title and link, full proposed AC, and why screenshot proof was useful; UI, repeat, and no-active dismissals are silent, and notification failures do not undo the dismissal. backlog→in_progress and backlog→done are rejected. Returns the updated goal with all fields.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Режим цели: standard или grove. Иммутабелен после mode_locked_at
`tags`	No	Новые теги
`type`	No	Новый тип: goal, milestone, task, habit
`title`	No	Новое название (макс. 500)
`goalId`	Yes	UUID цели
`status`	No	Новый статус: backlog, ready_for_work, in_progress, blocked, done, cancelled (checking_ac* выставляет система)
`deadline`	No	Новый дедлайн (ISO 8601)
`estimate`	No	Новая оценка
`priority`	No	Новый приоритет (1–5)
`description`	No	Новое описание
`attemptCommit`	No	git SHA коммита попытки (7–64 hex). Когда развёрнутая ревизия содержит его (предок, не равенство), post-deploy пробы цели стартуют сами по событию деплоя; повторная установка = новая попытка (отметки доставки и пробы сбрасываются); "" снимает
`dismissVisualAcSuggestion`	No	Отклонить advisory visual-AC; для ready_for_work это явный выбор «продолжить без предложения»

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

addedInput schema / properties / dismissVisualAcSuggestion

Added value: +{
+  "default": null,
+  "description": "Отклонить advisory visual-AC; для ready_for_work это явный выбор «продолжить без предложения»",
+  "type": "boolean"
+}

Changed1 schema field changedSep 3, 2026

changedInput schema / properties / status / description

Previous value: -"Новый статус: backlog, in_progress, blocked, done, cancelled"New value: +"Новый статус: backlog, ready_for_work, in_progress, blocked, done, cancelled (checking_ac* выставляет система)"

Changed1 schema field changedAug 28, 2026

changedInput schema / properties / attemptCommit / description

Previous value: -"git SHA коммита попытки (7–64 hex). Когда развёрнутая ревизия содержит его (предок, не равенство), post-deploy пробы цели стартуют сами по событию деплоя; повторная установка = новая попытка; \"\" снимает"New value: +"git SHA коммита попытки (7–64 hex). Когда развёрнутая ревизия содержит его (предок, не равенство), post-deploy пробы цели стартуют сами по событию деплоя; повторная установка = новая попытка (отметки доставки и пробы сбрасываются); \"\" снимает"

Changed1 schema field changedAug 28, 2026

addedInput schema / properties / attemptCommit

Added value: +{
+  "default": null,
+  "description": "git SHA коммита попытки (7–64 hex). Когда развёрнутая ревизия содержит его (предок, не равенство), post-deploy пробы цели стартуют сами по событию деплоя; повторная установка = новая попытка; \"\" снимает",
+  "type": "string"
+}

AddedJun 26, 2026

TDQS

A3.8/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description is exceptionally rich, disclosing dismissal persistence, Product Events notifications, and post-deploy probe behavior — all beyond the annotations. However, it CONTRADICTS the idempotentHint=true annotation: for attemptCommit it states 'повторная установка = новая попытка (отметки доставки и пробы сбрасываются)' (repeated installation = new attempt; delivery marks and probes reset), meaning a retried identical call produces a different state. This directly undermines the idempotency guarantee an agent would rely on. Per rubric, a contradiction scores 1 and must be flagged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core partial-update semantics, and every sentence carries essential information — the status matrix, the advisory freeze, and the dismissal rules are all load-bearing. The dismissal paragraph is dense and could be tightened, but there is no fluff or repetition for a complex 12-param tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex mutation tool with 12 parameters and no output schema, this is remarkably complete: it covers legal and illegal transitions, the advisory/freeze/dismiss flow, attemptCommit deployment behavior, notification semantics, and explicitly states the return value ('Returns the updated goal with all fields'). Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds genuine value beyond the schema: it explains attemptCommit's automatic post-deploy probe semantics and the '' clear convention, the dismissVisualAcSuggestion flow (advisory freeze, retry path, silent vs. notified dismissals), and the full status transition matrix that enriches the status param. This exceeds the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with 'Partial update of a goal — only the fields you pass are changed', a precise verb+resource+semantics statement. Explicitly lists updatable fields and distinguishes this from siblings like goal-create, goal-block, and goal-move. An agent knows exactly what this tool does and what it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit status transition matrix defining legal transitions (backlog→ready_for_work, ready_for_work→in_progress, in_progress→done|blocked|cancelled) and rejected ones (backlog→in_progress, backlog→done). Names the alternative goal-add-criterion explicitly with the condition that selects it (accept the visual AC suggestion vs. dismiss). Slightly weaker on broad exclusions for other sibling update tools, but the matrix largely covers routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Planner (proof-of-done) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?