Planner (proof-of-done)

project-update

Idempotent

Partial update of a project — only the fields you pass are changed; omitted fields are untouched. Updatable: title, slug, description, status (active/archived/paused), tags, icon (emoji), repositoryPath, repositoryUrl, sourceRef ({type:"git",url,ref} — remote-research source), clearSourceRef (true → сбрасывает Project.sourceRef в null; несовместим с sourceRef), isDefault, redTeamMode (optional/advisory/required), evidenceJudgeMode (off/optional/required), allowedGoalMode (any/grove_only), fmeaGenerationMode (off/on), escalationResolveTimeout (off/1h/4h/24h), escalationAutoResolveBy (none/planner-agent), escalationAutoResolveStrategy (suggest-edit/reject-default). Returns the updated project with all fields.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	Иконка (эмодзи, макс. 10 символов)
`slug`	No	Новый slug (только a-z, 0-9, дефис; должен быть уникальным)
`tags`	No	Новые теги
`title`	No	Новое название
`status`	No	Новый статус: active, archived, paused
`isDefault`	No	Сделать проектом по умолчанию
`projectId`	Yes	UUID проекта
`sourceRef`	No	Источник кода для remote-research: {type:"git",url,ref}
`description`	No	Новое описание
`redTeamMode`	No	Режим red-team: optional, advisory, required
`repositoryUrl`	No	URL репозитория
`clearSourceRef`	No	Установить sourceRef в null (отвязать репозиторий); несовместим с sourceRef
`repositoryPath`	No	Путь к репозиторию на сервере
`allowedGoalMode`	No	Разрешённые режимы целей: any, grove_only
`evidenceJudgeMode`	No	Режим судьи доказательств: off, optional, required
`fmeaGenerationMode`	No	FMEA-генерация: off, on
`escalationAutoResolveBy`	No	Авто-резолвер эскалации: none, planner-agent
`escalationResolveTimeout`	No	Таймаут эскалации: off, 1h, 4h, 24h
`escalationAutoResolveStrategy`	No	Стратегия авто-резолва: suggest-edit, reject-default

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 9, 2026

addedInput schema / properties / clearSourceRef

Added value: +{
+  "default": null,
+  "description": "Установить sourceRef в null (отвязать репозиторий); несовместим с sourceRef",
+  "type": "boolean"
+}

addedInput schema / properties / sourceRef

Added value: +{
+  "default": null,
+  "description": "Источник кода для remote-research: {type:\"git\",url,ref}",
+  "type": "object"
+}

AddedJul 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses the key behavioral trait that unmentioned fields are not reset, returns the updated project with all fields, and warns about sourceRef/clearSourceRef incompatibility. This adds meaningful semantic context for a mutation operation.

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 core semantic is front-loaded in the first clause, and the rest is a dense enumeration of all 19 updatable fields with their valid values. It is a long single sentence, which is somewhat hard to scan, but for a tool with 19 parameters it is information-efficient and avoids repetition.

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?

Given there is no output schema, the description correctly states that the tool returns the updated project with all fields. It also covers every parameter's valid values, the nested sourceRef object shape, the clearSourceRef incompatibility, and partial-update semantics. An agent has enough information to invoke the tool correctly across all documented fields.

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

Parameters3/5

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

Schema coverage is 100%, so the input schema already describes every parameter in detail. The description does add value by enumerating valid values for enum-like parameters (e.g., status, redTeamMode, escalationResolveTimeout) and repeating the sourceRef shape, but this mostly mirrors the schema rather than adding substantial new meaning. Baseline 3 is appropriate.

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 starts with a precise verb and resource: 'Partial update of a project'. It clearly distinguishes this from sibling tools like project-create, project-delete, and project-get by emphasizing that only passed fields are changed while omitted fields remain untouched. This is a specific, unambiguous purpose.

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 clearly establishes when this tool should be used: when you need to update a project partially. It also provides an important exclusion by noting that clearSourceRef is incompatible with sourceRef. However, it does not explicitly mention alternatives or state 'do not use for creating/deleting projects', though the sibling names make that inferable.

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?