Skip to main content
Glama

Items Check Manifest

items_check_manifest
Read-only

Verify every item reference in a manifest against an items.json registry to catch dangling references before merging.

Instructions

Reference-integrity guard (#140 C1): check every item-reference in a manifest ({"item":""} on a component/instance) resolves against an items.json registry. Returns {ok, problems} — a dangling item-ref is caught before a merge, removing the "a part is its filename" fragility.

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": {
      "manifest": "<manifest>",
      "registry": "<registry>"
    },
    "name": "items_check_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYes
registryYes
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

A3.7/5.0
Behavior4/5

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

readOnlyHint already tells the agent this is a non-mutating check, so the description is not required to establish the safety profile. It nonetheless adds real behavioral context beyond the annotations: the return shape {ok, problems}, the registry it resolves against, and the failure mode it prevents. It stops short of explaining what a 'problem' entry contains or whether the registry must already be loaded.

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?

One front-loaded sentence plus a return-shape clause; nothing is padded and the purpose comes first. The internal tracker tag '(#140 C1)' is noise the calling agent cannot use, a minor deduction.

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?

With no output schema, the description does the right thing by declaring the return shape {ok, problems}. It covers intent, the reference format, the registry, and the return contract. What is left unaddressed — how manifest and registry are supplied (path vs. inline), and what counts as a problem — is the remaining gap for a 3-parameter tool.

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 description coverage is only 33% — manifest and registry are bare strings with no description. The description partially compensates by defining the manifest's reference syntax and identifying the registry as items.json, but it does not say whether either argument is a path, an inline JSON body, or a workspace-relative name, which is exactly the ambiguity the schema leaves open.

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 and resource: it checks every item-reference in a manifest against an items.json registry, and it even spells out the reference shape ({"item":"<id>"}) being validated. That is far more concrete than a restated title. It never names a sibling, though, so it does not distinguish itself from adjacent checks like items_validate, validate_manifest, or project_check_references.

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?

'a dangling item-ref is caught before a merge' implies the intended timing (as a pre-merge gate), which is a useful, if indirect, trigger. But there is no explicit when-to-use/when-not-to-use statement and no named alternative among the many validation siblings (items_validate, project_check_references, validate_manifest). The agent has to infer which check it wants.

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