Skip to main content
Glama

Items Resolve

items_resolve
Read-only

Resolve an item ID to its artifact files through an items.json registry, preserving references when files are renamed or moved and reporting dangling references.

Instructions

Resolve an item-reference (an item id) to its artifact file(s) against an items.json registry — identity, not a bare path, so renaming/moving a file updates the item's files[] without breaking references. Returns {ok, files}, or {ok:false, problems} on a dangling reference (an unknown item id).

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": {
      "registry": "<registry>",
      "item": "<item>"
    },
    "name": "items_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is known. The description adds genuine behavioral value: the identity-not-path semantics (renaming/moving updates files[] preserve references) and explicit error behavior ({ok:false, problems} on a dangling reference).

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?

Two sentences, front-loaded with the verb and resource. The rationale clause is slightly long but earns its place by explaining why identity references matter and what failures look like.

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?

For a read-only, no-output-schema tool, the description covers the return shape ({ok, files}) and the failure shape, which is what an agent needs. Only the exact meaning of the `registry` argument remains under-specified, a minor gap.

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 coverage is only 33% (only workspace is documented). The description compensates for both undocumented params by tying `item` to 'an item id' and `registry` to 'an items.json registry', which is meaningful beyond the bare titles. It still omits format details (is registry a path, filename, or key?) so it lands at baseline.

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?

Specific verb+resource: 'Resolve an item-reference (an item id) to its artifact file(s) against an items.json registry', plus a clarifying rationale (identity not a bare path). This clearly distinguishes it from items_validate/items_new/items_check_manifest by describing the resolution act, though it does not name those siblings explicitly.

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 context is implied by the description — you call it to turn an item id into files. But there is no explicit when-to-use/when-not versus items_validate, items_check_manifest, or resolve_edge/resolve_face, and no prerequisites (e.g., registry must exist) are stated.

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