Skip to main content
Glama
kznlabs

labsUI

by kznlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update labsUI items

update
DestructiveIdempotent

Bring installed labsUI items to the current version: replace unedited files, merge edited ones three-way, and report conflicts or kept files; use dryRun to preview changes.

Instructions

Bring installed labsUI items to this labsUI version. Unedited files are replaced; edited ones are merged three ways from the version that installed them, with conflict markers where both sides changed the same lines. Returns each changed item as replaced, merged, conflicts (with the files to resolve) or kept with the reason. Run diff first to see local edits; dryRun previews. Only for installed items: new ones go through add.

Input Schema

NameRequiredDescriptionDefault
namesNoInstalled item names, e.g. button. Empty: all installed items.
dryRunNoReport what would change, write nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedInput schema / properties / names / description
      Previous value: -"Installed item names, e.g. button. Empty: every installed item."New value: +"Installed item names, e.g. button. Empty: all installed items."
  2. 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: +"Installed item names, e.g. button. Empty: every installed item."
  3. First observedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, it discloses the actual mutation semantics: unedited files are replaced, edited files are three-way merged from the installing version, conflict markers appear when both sides change the same lines, and each item returns as replaced, merged, conflicts, or kept with a reason. This is exactly the kind of destructive-behavior context the annotations alone do not provide.

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?

The description is compact and front-loaded: purpose first, then replacement/merge behavior, return categories, inspection alternatives, and scope restriction. Every sentence carries useful information.

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?

With no output schema, the description still explains the return categories (replaced, merged, conflicts with files to resolve, kept with reason) and the preview path (dryRun, diff). For a destructive update tool, this gives the agent enough to call and interpret it correctly.

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%, so the schema already documents both parameters and their defaults. The description reinforces dryRun as a preview mode but adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 states a specific action ('Bring installed labsUI items to this labsUI version') with a clear scope (installed items) and explicitly separates itself from 'add' for new items and 'diff' for inspection. An agent can distinguish this from siblings 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?

It names the alternative tools and the conditions that select them: 'Run diff first to see local edits; dryRun previews' and 'Only for installed items: new ones go through add.' This is explicit when-to-use and when-not-to-use guidance.

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