Skip to main content
Glama

Add labsUI items

add
Idempotent

Installs labsUI items into your project by copying each item and its imported files and installing npm packages, while keeping existing files unchanged.

Instructions

Install labsUI items into the project: copies each item and everything it imports, then installs their npm packages. Existing files are kept, never overwritten. Returns the files written, the packages installed, dependencies kept that differ from this version (call update on them) and anything to mount once in the root layout. Needs init first; dryRun previews. To bring installed items to a newer version, use update instead.

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": {
      "names": "<names>"
    },
    "name": "add"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesItem names as search lists them, e.g. button or date-picker.
dryRunNoReport what would change, write nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • changedInput schema / properties / dryRun / description
      Previous value: -"Report, write nothing."New value: +"Report what would change, write nothing."
    • addedInput schema / properties / names / description
      Added value: +"Item names as search lists them, e.g. button or date-picker."
  2. First observedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare non-destructive, idempotent, open-world behavior; the description goes further by disclosing the non-overwrite guarantee ('Existing files are kept, never overwritten') and the shape of the result (files written, packages installed, mismatched kept dependencies, mount instructions). It also flags the follow-up action needed for outdated dependencies, which is real behavioral context an agent cannot get from the annotations.

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

Conciseness5/5

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

Three dense sentences, front-loaded with the action and followed by effects, constraints, return shape, and the alternative. Every clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by summarizing the return payload and the post-install mount step. Combined with the disclosed prerequisite (init) and overwrite policy, an agent has enough to invoke this correctly on the first try.

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 100% with descriptions for both `names` and `dryRun`, so the schema carries parameter meaning. The description's 'dryRun previews' only restates the schema's 'Report what would change, write nothing' and adds no naming/format guidance beyond the pattern already given. Baseline 3 applies.

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 with scope: 'Install labsUI items into the project: copies each item and everything it imports, then installs their npm packages.' It also explicitly contrasts with the sibling 'update' tool, so an agent can distinguish it from update/init/search without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit prerequisites ('Needs init first'), a preview path ('dryRun previews'), and a named alternative with the condition that selects it ('To bring installed items to a newer version, use update instead'). Nothing is left to inference about when to pick this tool.

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