Skip to main content
Glama
Sign In

PixelGlass

by co.pixelglass
OverviewDiscussionsAdmin

Resolve a theme update

resolve_theme_update
Destructive

On one site of the account, named in site. Settles an open update_theme merge by side — sides maps every conflicted file to "ours" (the site's lines) or "theirs" (the release's) and commits the merge — or, with undo, takes the update back while it is not live yet: the open merge abandoned, or the merged release dropped while it waits and nothing was edited after it. A release already live is taken back with restore_theme_revision. Editing the files yourself keeps more; this is the quick way. Admins only.

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": {
      "site": "<site>",
      "theme": "<theme>"
    },
    "name": "resolve_theme_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site to work on, as list_sites names it
undoNo
sidesNoEvery conflicted path to a side
themeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and non-idempotent, but the description goes further by disclosing what is actually destroyed (the open merge abandoned, or the merged release dropped) and the precondition that nothing was edited after it. It also carries an authorization requirement ('Admins only') that no annotation expresses.

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?

Almost every clause earns its place — mode semantics, undo limits, the live-release escape hatch, the manual alternative, and the admin gate. Structure suffers, however: the whole definition is one ~110-word sentence stitched with em-dashes and 'or', making the two operating modes harder to parse than necessary.

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

Completeness4/5

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

For a destructive, nested-object tool with no output schema and only 50% schema coverage, the description covers mode selection, preconditions, destruction scope, and permissions. It leaves return behavior and what happens if `sides` omits a conflicted path unstated, which is a modest gap rather than a blocking one.

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?

With 50% schema coverage, the description earns credit for explaining `sides` as a per-conflicted-file mapping and defining 'ours' as the site's lines vs 'theirs' as the release's, plus the exact effect of `undo` — details absent from the schema. The `theme` parameter gets no explanation anywhere, which keeps it off a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource pair ('settles an open update_theme merge by side') and scopes it to one site, making it clearly distinct from update_theme and restore_theme_revision. The only blemish is the opening fragment 'On one site of the account, named in site.', which reads as a dangling clause rather than a stated purpose.

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 states exactly when to use each mode: `sides` when a merge is open and must be committed, `undo` only while the update is not live, and restore_theme_revision once a release is live. It also names the manual alternative ('editing the files yourself keeps more; this is the quick way'), giving the agent a real trade-off to route on.

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

All PixelGlass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources