Skip to main content
Glama
Sign In
PaintPilot

PaintPilot

by lavalava45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_guard_keep_logical_layer

Commit a visually accepted temporary component to its predeclared independent unit using journal-bound hypothesis_id and layer_id without altering pixels or layer structure.

Instructions

Commit a visually accepted temporary component on a predeclared independent unit using its journal-bound hypothesis_id and layer_id; does not alter pixels or layer structure. A temporary composition-scaffold unit cannot be promoted or relabelled.

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": {
      "request_key": "<request_key>",
      "document_id": "<document_id>",
      "hypothesis_id": "<hypothesis_id>",
      "layer_id": "<layer_id>"
    },
    "name": "photoshop_guard_keep_logical_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idYes
rationaleNoOptional audit/artistic guidance for why this already-bound temporary owner is being promoted.
document_idYes
request_keyYes
hypothesis_idYes
scene_ownership_planNoRequired when this temporary owner is the first committed owner and no durable scene ownership plan exists yet. Must predeclare the owner being kept; later keep calls reuse the durable plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0-preview.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully states that pixels and layer structure are not altered, and that composition-scaffold units cannot be promoted or relabelled, but it omits idempotency, request_key behavior, ownership-state side effects, and failure modes.

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 two tightly written sentences with the core action and constraint front-loaded. Every sentence adds relevant meaning without repetition.

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

Completeness2/5

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

This is a complex tool with six parameters including a nested scene ownership plan, no annotations, and no output schema. The description covers the core commit semantics but leaves major gaps around conditional requirements, identifier contracts, and expected state changes.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description should compensate, but it only explains hypothesis_id and layer_id as journal-bound identifiers. It does not clarify request_key, document_id, rationale, or when the complex scene_ownership_plan object is required.

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 gives a specific verb and object: commit a visually accepted temporary component on a predeclared independent unit using journal-bound IDs. It also states the main exclusion for composition-scaffold units, though it does not explicitly differentiate itself from any sibling guard tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'visually accepted temporary component' and 'predeclared independent unit' imply this is used only after visual acceptance and prior declaration. However, there is no explicit when-to-use guidance against alternatives such as reconcile or cycle-auto, and no clear prerequisite checklist.

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