Skip to main content
Glama

solution_update

Destructive

Dry-run or apply adding, removing, or reordering X++ projects while reconciling dependencies and project configuration.

Instructions

Dry-run or add, remove, or reorder X++ projects with dependency and configuration reconciliation.

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>",
      "action": "<action>"
    },
    "name": "solution_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo
actionYes
dryRunNo
projectNo
projectGuidNo
projectGuidsNo
expectedSha256No

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
dryRunNo
changesNo

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, and non-idempotent, so safety is covered structurally. The description adds real value by disclosing that dependency and configuration reconciliation happen as a side effect and that dry-run is available, but it omits what gets destroyed on remove, how conflicts surface, and how to use expectedSha256 as a concurrency guard.

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 sentence with the verbs and the dry-run option front-loaded and no filler. It is efficient, though the density means reconciliation and dry-run get equal weight without structure to separate them.

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 mutation with 8 undocumented parameters and a nested object, the description is far too thin; the presence of an output schema excuses only return-value detail. Key operational facts — action-to-parameter mapping, the concurrency guard, and removal consequences — are absent.

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 8 parameters, including a nested project object, and the description adds meaning only for dryRun. It never explains the distinction between project versus projectGuid versus projectGuids, which action requires which parameter, or the expectedSha256 precondition — the highest-risk gaps in the definition.

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 (add, remove, reorder) and a specific resource (X++ projects), plus the reconciliation behavior, so an agent can tell what the tool mutates. It stops short of differentiating itself from siblings like project_update or artifact_update, so it is clear but not sibling-aware.

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 that a dry-run mode exists; there is no statement of when to choose this over project_update, artifact_update, or solution_inspect, and no prerequisites. An agent must infer the routing decision entirely.

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