Candor UI docs

What changed in one Candor UI item between two versions

item_changes

Read-onlyIdempotent

What changed in one item between two released versions, from facts only, to plan an update and write its PR: props added, removed or retyped, exports and LocaleProvider string keys added or removed, and files touched, from each release's API record; then the CHANGELOG entries in the range that name the item or its exports. Plain words first, then the same as JSON. Records start at 2.7.0: for an earlier version it says "not recorded before 2.7.0" and what is known from the first recorded release on, never a guess. from is the version the project has (candor-lock.json records it), and defaults to the one the server URL passes (?kit=, written by npx candor-ui mcp); to defaults to the latest. Example arguments: { "item": "plan", "from": "2.7.0", "to": "2.8.0" }

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

Input Schema

Name	Required	Description
`to`	No	The version to compare with. Default: the latest.
`from`	No	The version installed, e.g. "2.7.0" (candor-lock.json records it). Default: the version the server's URL passes (`?kit=`), which `npx candor-ui mcp` writes from the lockfile.
`item`	Yes	The registry name, e.g. "plan" or "approval-request".

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses important behavior: results come from facts in each release's API record and CHANGELOG, output is plain words then JSON, and versions before 2.7.0 are explicitly reported as not recorded rather than guessed. This is strong behavioral context for a read-only diff tool.

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?

The description is front-loaded with the core purpose and then layers in data sources, output shape, version caveats, and defaults. It is dense but well structured; a few phrases are repeated, but most sentences carry actionable 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?

For a version-diff tool with no output schema, the description explains what data is compared, what categories are returned, the output format, and how unavailable historical versions are handled. Together with annotations and the fully documented schema, this is complete enough for an agent to invoke it 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%, so the schema already documents all three parameters. The description still adds useful meaning by clarifying that `from` is the installed version from candor-lock.json, that defaults can come from the server URL's `?kit=`, and by giving example arguments.

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 verb and resource: what changed in one Candor UI item between two released versions. It names the exact diff categories (props, exports, LocaleProvider string keys, files touched, CHANGELOG entries), so the agent can distinguish it from sibling documentation and lookup tools.

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?

It gives a clear use case: to plan an update and write its PR. It also explains version defaults and where `from` comes from, though it does not explicitly compare against alternative tools or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Candor UI docs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.