Skip to main content
Glama

New Item

items_new

Allocates a sequential part number, registers a new item in an items.json sidecar (creating it if absent), and writes the updated registry.

Instructions

Allocate a non-significant sequential part number and register a new item in an items.json sidecar (created if absent), writing it back. The reserved rev / lifecycle fields are seeded with held defaults (the #141 state machine, not C1).

registry: path to the items.json sidecar (created if it does not exist). item: the new item's stable logical id (what manifests reference). files: optional list of artifact paths the item maps to. metadata: optional free-form, queryable attributes (where "meaning" lives).

Returns {part_number, item, registry}.

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_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
filesNo
metadataNo
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the sidecar is created if absent, the file is written back, the part number is sequential and non-significant, and rev/lifecycle fields are seeded with held defaults rather than C1 values.

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?

Front-loaded with the core action, then a clean per-parameter breakdown and a return-shape line; almost no waste. The one opaque aside ('the #141 state machine, not C1') costs a little comprehension without adding actionable guidance.

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 mutating tool with no output schema, the description supplies the return shape ({part_number, item, registry}) and the write semantics. What is missing is failure behavior: whether the call errors or overwrites when the item id already exists in the registry, which matters for a 'new' operation.

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?

With only 20% schema coverage, the description carries most of the load and does so for four of five parameters: registry (path, created if absent), item (stable logical id referenced by manifests), files (optional artifact paths), metadata (free-form queryable attributes). Only the workspace parameter is left to the schema, and the item id format is unspecified.

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?

States a specific verb and resource: allocates a sequential part number and registers a new item in an items.json sidecar. This is clearly the creation primitive among the items_* siblings (items_validate, items_resolve, items_check_manifest), so an agent can pick it without opening the schema.

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 description implies when to use it (you want a new registry entry with an allocated part number) and hints at the lifecycle model ('the #141 state machine, not C1'), but it never states prerequisites or routes the agent to an alternative, e.g. items_resolve for existing entries or items_validate before writing.

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