Skip to main content
Glama

Project Resolve Manifest

project_resolve_manifest
Destructive

Resolves item-ref components to file components and writes a merge-ready manifest for merge_assembly, so renaming or moving a CAD file updates references in one place.

Instructions

Resolve a project's item-ref components to file components and write a merge- ready manifest (issue #143 / D1, the deferred #140 seam). Each component naming an item (items.json identity, not a bare path) is lowered to a {file} component with the CAD artifact resolved from the registry, so merge_assembly consumes the result unchanged — renaming/moving a file updates the item's files[] in one place without breaking any reference.

project: path to the project.json container. out: output manifest path (defaults to .resolved.json next to it).

Returns {path, lowered} — the written path and the lowered manifest object; a dangling item-ref fails loudly.

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": {
      "project": "<project>"
    },
    "name": "project_resolve_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNo
projectYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to re-establish that this writes. It adds real value beyond that: the output filename default, the fact that a dangling item-ref fails loudly, and the return shape. It stops short of describing scope of overwrite (does it clobber an existing .resolved.json?) or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and downstream consumer come first, which is good. But the parenthetical '(issue #143 / D1, the deferred #140 seam)' and the verbose item-ref/files[] explanation consume space that an agent invoking the tool doesn't need; the description could be roughly half its length without losing operational detail.

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?

There is no output schema, but the description compensates by describing the return object ({path, lowered}) and the failure mode. Combined with the default output path and the downstream contract with merge_assembly, an agent has enough to call this correctly; only workspace behavior is unaddressed.

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 only 33% (only workspace is documented in the schema), so the description needs to compensate. It does so for `project` (path to project.json container) and `out` (defaults to <manifest>.resolved.json next to it), covering the two parameters an agent actually has to reason about. `workspace` is left to the schema, which is a minor gap.

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 uses a specific verb+resource pair ('resolve ... item-ref components to file components and write a merge-ready manifest') and explicitly positions the output as input to merge_assembly. An agent can distinguish this from validate_manifest, items_resolve, or merge_assembly itself.

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?

Usage is implied rather than stated: the description says the result is consumed by merge_assembly unchanged, which tells the agent roughly when to reach for it. But it never names the neighboring tools (items_resolve, validate_manifest, items_check_manifest) or gives an explicit when-not condition.

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

Deploy Server

Other Tools