Skip to main content
Glama

project_update

Destructive

Create or update an .rnrproj file with reconciled artifacts and optional solution registration. Use dry-run mode to preview changes before writing.

Instructions

Dry-run or create/update an .rnrproj with reconciled artifacts and optional solution registration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "name": "<name>",
      "model": "<model>",
      "artifacts": "<artifacts>"
    },
    "name": "project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidNo
nameYes
pathYes
rootNo
modelYes
dryRunNo
artifactsYes
solutionPathNo
expectedSha256No
solutionProjectNameNo
solutionExpectedSha256No

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
dryRunNo
changesNo
projectGuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is known. The description usefully adds that the target is an on-disk .rnrproj and that a dry-run mode exists, but it says nothing about what gets overwritten or truncated when a project already exists, nor that the sha256 parameters guard against clobbering changed files. With annotations covering the safety bar, this is adequate but not rich.

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?

A single front-loaded sentence with no filler; the dry-run distinction is placed first where it matters most. It is efficient, though at this brevity for an 11-parameter destructive tool it leans toward under-specification rather than true conciseness.

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

Completeness2/5

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

For a destructive, non-idempotent write with 11 undocumented parameters and no description coverage, one sentence is not enough. An output schema exists so return values need not be explained, but the description omits preconditions, overwrite behavior, and the role of the integrity-hash parameters, leaving an agent unable to call it safely.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, so the description carries the full burden and largely fails it. It gestures at artifacts ('reconciled artifacts') and solution registration, but says nothing about path, name, model, root, guid, expectedSha256, solutionExpectedSha256, or solutionProjectName — the concurrency-guard semantics of the sha256 fields are especially opaque.

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

Purpose4/5

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

The description names a specific verb set (dry-run or create/update) and a specific resource (.rnrproj project file), plus the two distinguishing behaviors: reconciled artifacts and optional solution registration. It is clear what the tool does, but it never contrasts itself with artifact_update or solution_update, which are adjacent write tools a caller could easily confuse it with.

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

Usage Guidelines2/5

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

The only usage signal is the dry-run-vs-write split, which is already implied by the dryRun parameter defaulting to true in the schema. There is no statement of when to choose this over artifact_update, solution_update, or project_inspect, no preconditions, and no note on whether the project file must already exist.

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