Skip to main content
Glama
KasayoDotCom

Identity Forge MCP

Official

Update a saved design kit

update_theme

Update an existing design kit in place when the brand changes, preserving its slug and publication state so existing links keep working. Deep merges partial kit edits and applies overrides.

Instructions

Edit a design kit you already saved, in place. This OVERWRITES the stored kit without asking: the slug, id and publication state all stay the same, so everything already pointing at that kit follows the edit, including brand variations that reference it, any client share link that serves it, and a repo that installed its registry entry. The overwrite itself has no undo, but it is recorded: every save mints a version, so the state you replaced stays readable through list_kit_versions and get_kit_version, and diff_kit_versions shows exactly what your edit moved. Reach for remix_theme instead when you want the original left alone, which is usually the right call while you are still exploring directions; use this one when the kit is the brand and the brand has genuinely changed. It only edits kits saved under your key. A catalog kit, another user's kit, or an unknown slug all return 404 alike. kit is deep merged over the stored payload, so you state only what moves and everything else survives, and overrides applies on top of that merge. The one thing you cannot change is the slug itself: it is the kit's public handle and moving it would break every link already using it, so a payload carrying a different slug is rejected with 400 rather than quietly ignored. Pass expectedUpdatedAt from the last read to get a 409 instead of silently overwriting a change someone else made in between; the 409 body carries the current marker so you can re-read, reapply and retry. Requires the kits:write scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kitNoPartial kit JSON, deep merged over the stored kit. Unmentioned fields are kept. A `slug` different from the kit's own is rejected.
nameNoNew display name. Omit to leave the name unchanged.
slugYesPermanent id or slug of a kit saved under your own key. Catalog and other users' kits are not editable.
overridesNoToken, color, font and facet writes applied on top of the merged kit.
expectedUpdatedAtNoThe updatedAt you last read for this kit. Pass it to reject the write with 409 if the kit changed meanwhile.
Behavior5/5

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

With no annotations, the description carries full burden, and it excels: discloses overwrite-without-undo, versioning, deep merge behavior, slug immutability with 400 rejection, 404 uniformity, optimistic concurrency with 409 and retry flow, and required scope. This is exceptional behavioral disclosure.

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 dense but every sentence earns its place. It front-loads the core overwrite action, then systematically covers versioning, alternatives, scope, merge behavior, slug restriction, concurrency, and auth—all in a logical order with zero 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?

For a complex mutation tool with 5 params, nested objects, no output schema, and no annotations, the description covers all essential contexts: behavior, side effects, error cases, concurrency, scope, and alternatives. It leaves no material ambiguity for an AI agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds crucial semantics beyond field labels: it explains the deep merge for `kit`, that `overrides` applies on top, why slug changes are rejected, and how `expectedUpdatedAt` enables concurrency control. This transforms raw parameters into an actionable mental model.

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 opens with a clear, specific verb and resource: 'Edit a design kit you already saved, in place.' It immediately distinguishes itself from siblings like remix_theme (copy) and create_theme (new kit), and the overwrite semantics are unambiguously stated.

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 guidance is given: 'Reach for remix_theme instead when you want the original left alone... use this one when the kit is the brand and the brand has genuinely changed.' It also clarifies scope (only kits saved under your key, others return 404), giving clear when-to and when-not-to.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KasayoDotCom/identityforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server