Skip to main content
Glama

artifact_update

Destructive

Validate and update or rename artifact XML and companion payloads, reconciling indexed project memberships in one transaction with dry-run support.

Instructions

Dry-run or validate and update/rename artifact XML and any companion payload, reconciling indexed project memberships in one transaction.

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>",
      "content": "<content>"
    },
    "name": "artifact_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo
dryRunNo
contentYes
projectPathNo
labelContentNo
solutionPathNo
expectedSha256No
projectExpectedSha256No
resourceContentBase64No
companionExpectedSha256No

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
actionNo
dryRunNo
impactNo
changesNo
artifactNo
previousIdNo
impactTruncatedNo
solutionValidatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false, so the safety profile is known. The description adds genuinely new behavioral facts beyond that: the operation supports a dry-run/validate phase, it touches a companion payload in addition to the XML, and membership index reconciliation happens atomically in one transaction. It still does not warn about overwrite risk or permission requirements, which is why this is a 4 rather than a 5.

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?

It is a single dense sentence that front-loads the dry-run/validate distinction before the mutation, with no filler. It is arguably overpacked — the atomicity and membership-reconciliation clauses crowd out simpler parameter facts that would be more valuable.

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

Completeness3/5

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

An output schema exists, so return values need not be described. However, for an 11-parameter destructive mutation with zero schema description coverage, the description should say more about the concurrency tokens and the meaning of root/path. As written an agent could invoke it without understanding that expectedSha256 guards against clobbering concurrent edits.

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?

With 11 parameters at 0% schema description coverage, the description carries the full explanatory burden and largely fails. It maps loosely to content ('artifact XML'), companion payload/label content ('companion payload'), and project/solution membership ('indexed project memberships'), but the optimistic-concurrency parameters (expectedSha256, projectExpectedSha256, companionExpectedSha256), root, and the default-on dryRun semantics are never explained. For a destructive tool, leaving the concurrency tokens undocumented in both schema and description is a serious gap.

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 specific verbs and resources: validate/dry-run, then update or rename artifact XML plus any companion payload, with indexed project memberships reconciled. That distinguishes it from siblings like artifact_remove and artifact_build implicitly through the mutation-plus-payload scope. It stops short of naming which sibling to use instead for pure validation, so it isn't fully differentiated.

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

Usage Guidelines3/5

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

The phrase 'Dry-run or validate and update' implies the two modes of operation and hints that a preview should precede a real change, which is real, if compressed, usage guidance. There is no explicit statement of when to choose this tool over artifact_validate or artifact_remove, and no prerequisite conditions are given.

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