Skip to main content
Glama

Planner (proof-of-done)

by com.monopoly-gold.planner
OverviewDiscussionsAdmin

goal-create

Create a goal/task/milestone/habit in the planning tree. Two modes: grove (default) — enforces acceptance criteria gate on status transitions (AC required before ready_for_work, file-evidence per AC before done); standard — carries the same AC but without the evidence gate (advisory linting only). Returns the created goal with id, webUrl, mode, and nextStep hint. For an explicit visible UI result, the response may include an advisory visualAcSuggestion; adopt its criterion through goal-add-criterion with visualEvidenceSuggested=true, or ignore it. Every goal must belong to a project (pass projectId or inherit from parent).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoРежим: grove (default) или standard. Grove enforce-ит I_start на ready_for_work и I₃ на done; standard несёт те же AC, но без evidence-гейта
tagsNoТеги
typeNogoal / milestone / task / habit (default: task)
titleYesНазвание цели (макс. 500)
statusNobacklog (default) / ready_for_work (объявить контракт готовым; grove в проекте с обязательным red-team объявляется только через goal-update)
deadlineNoДедлайн ISO 8601
estimateNoОценка
parentIdNoUUID родителя (null = root)
priorityNoПриоритет 1–5 (default: 3)
projectIdNoUUID проекта
descriptionNoОписание
acceptanceCriteriaNoСписок AC: строка (pre-merge критерий) или объект {text, probeClass?: pre-merge|post-deploy, probeSpec?}. post-deploy критерий обязан нести исполнимую пробу probeSpec {method, url, expect:{http_code, body:{field: expectedValue}}} — иначе error=probe_required; probeSpec без probeClass = post-deploy. Grove: опциональны на create, обязательны до объявления ready_for_work, блокирующий quality-линтер. Standard: описательные, линтер advisory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / acceptanceCriteria / description
      Previous value: -"Список AC: строка (pre-merge критерий) или объект {text, probeClass?: pre-merge|post-deploy, probeSpec?}. post-deploy критерий обязан нести исполнимую пробу probeSpec {method, url, expect:{http_code, body:{field: expectedValue}}} — иначе error=probe_required; probeSpec без probeClass = post-deploy. Grove: опциональны на create, обязательны до перехода в in_progress, блокирующий quality-линтер. Standard: описательные, линтер advisory"New value: +"Список AC: строка (pre-merge критерий) или объект {text, probeClass?: pre-merge|post-deploy, probeSpec?}. post-deploy критерий обязан нести исполнимую пробу probeSpec {method, url, expect:{http_code, body:{field: expectedValue}}} — иначе error=probe_required; probeSpec без probeClass = post-deploy. Grove: опциональны на create, обязательны до объявления ready_for_work, блокирующий quality-линтер. Standard: описательные, линтер advisory"
    • changedInput schema / properties / mode / description
      Previous value: -"Режим: grove (default) или standard. Grove enforce-ит I_start на in_progress и I₃ на done; standard несёт те же AC, но без evidence-гейта"New value: +"Режим: grove (default) или standard. Grove enforce-ит I_start на ready_for_work и I₃ на done; standard несёт те же AC, но без evidence-гейта"
    • changedInput schema / properties / status / description
      Previous value: -"backlog (default) / in_progress"New value: +"backlog (default) / ready_for_work (объявить контракт готовым; grove в проекте с обязательным red-team объявляется только через goal-update)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / acceptanceCriteria / description
      Previous value: -"Список AC-формулировок. Grove: опциональны на create, обязательны до перехода в in_progress, блокирующий quality-линтер. Standard: описательные, линтер advisory"New value: +"Список AC: строка (pre-merge критерий) или объект {text, probeClass?: pre-merge|post-deploy, probeSpec?}. post-deploy критерий обязан нести исполнимую пробу probeSpec {method, url, expect:{http_code, body:{field: expectedValue}}} — иначе error=probe_required; probeSpec без probeClass = post-deploy. Grove: опциональны на create, обязательны до перехода в in_progress, блокирующий quality-линтер. Standard: описательные, линтер advisory"
    • removedInput schema / properties / acceptanceCriteria / items / type
      Removed value: -"string"
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only state readOnly=false and idempotent=false. The description adds meaningful behavioral detail: return shape (id, webUrl, mode, nextStep), enforcement differences between grove and standard modes, potential probe_required errors, and the advisory visualAcSuggestion response behavior.

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?

The description is dense but organized into a compact main narrative plus structured parameter details. Some phrasing is mixed-language and slightly redundant, but the key behavior, return value, and constraints are presented without excessive filler.

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

Completeness4/5

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

The description covers return value, mode behavior, acceptance criteria requirements, project membership, and an important error case. It does not enumerate all possible errors or side effects, but for a create operation with no output schema, the context provided is sufficient.

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% with descriptions for all 12 parameters, including defaults, constraints, and nested acceptance criteria structure. A few descriptions are terse or jargon-heavy (e.g., 'I_start', 'I₃', 'Теги'), but overall the semantics are sufficiently clear for invocation.

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?

The description states a specific verb ('Create') and resource ('goal/task/milestone/habit in the planning tree'), including constraints like project membership and mode behavior. It clearly distinguishes the creation action from related goal operations.

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?

The description gives practical usage context, such as when ready_for_work must be declared via goal-update and when post-deploy criteria require probes. It does not explicitly enumerate sibling alternatives, but the creation scope and the goal-update status caveat provide reasonable guidance.

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) toolsInspect
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