Skip to main content
Glama

Diff installed labsUI items

diff
Read-only

Compare installed labsUI items with the current version to see per-file patches, formatting-only differences, and whether each change is upstream, local, or both before updating.

Instructions

Compare installed labsUI items with this labsUI version. Returns a unified patch per changed file, from the registry file to the project file (+ lines exist only in the project), with formatting: true when only blank lines or indentation differ and changedBy saying whose change it is since the installed version: upstream (only labsUI changed it; update replaces the file), local (only you did; update keeps it) or both (update merges), unset when that version can't be fetched; matching items are left out, a named item that isn't installed comes back with installed: false, and when nothing differs it says so. Use it before update to see what it will do. Needs init.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNoInstalled item names, e.g. button. Empty: all installed items.

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. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / names / description
      Added value: +"Installed item names, e.g. button. Empty: every installed item."
  3. First observedv0.1.3

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, yet the description discloses the return shape and non-obvious semantics: + lines exist only in the project, a `formatting: true` flag for whitespace-only differences, the upstream/local/both/unset values of changedBy and how each affects a subsequent update, omission of matching items, and installed:false for named-but-absent items.

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?

Purpose and diff direction are front-loaded, and every clause carries real information for a tool with no output schema. However, the second half is one long colon-and-semicolon chain (changedBy values, formatting, omissions, nothing-differs case) that would read more reliably as a short bulleted list.

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 must carry the entire return contract, and it does: per-file patch, diff direction, the formatting flag, all four changedBy states and their update implications, omission rules, and the no-difference case. Combined with the init prerequisite, an agent has enough to call and interpret this correctly.

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?

Schema coverage is 100% and the single `names` parameter is fully documented there, so baseline is 3. The description adds meaning beyond the schema by explaining the observable consequence of naming an item that isn't installed (it comes back with installed: false) and by implying items left unnamed/matchless are dropped from the result.

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 ('Compare installed labsUI items with this labsUI version') and immediately clarifies the returned artifact ('a unified patch per changed file, from the registry file to the project file'). An agent can distinguish it from sibling `view` or `search` 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 Guidelines4/5

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

Gives an explicit triggering workflow ('Use it before update to see what it will do') and a hard prerequisite ('Needs init'), plus the update-behavior consequences of each changedBy value. It stops short of naming when not to use it (e.g., use `view` to read a single item's rendered content), so it is clear context without full exclusions.

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