Skip to main content
Glama
Sign In

Layerre

by com.layerre
OverviewDiscussionsAdmin

Update layer

layerre_update_layer
Idempotent

Update layer properties like position, text content, image URL, styling, etc. Triggers background preview regeneration.

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": {
      "template_id": "<template_id>",
      "layer_id": "<layer_id>"
    },
    "name": "layerre_update_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoNew X position in pixels
yNoNew Y position in pixels
nameNoNew layer name
layer_idYesThe UUID of the layer to update
positionNoZ-order position (0=bottom/back, higher=top/front)
propertiesNoUpdated layer properties
template_idYesThe UUID of the template

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-readOnly, so the safety profile is covered. The description adds real value beyond that by disclosing the side effect that background preview regeneration is triggered, which is non-obvious and affects cost/timing decisions. It stops short of saying whether the response waits for regeneration.

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?

Two short sentences, capability stated first and side effect second, with zero filler. Nothing could be cut without losing information.

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

Completeness3/5

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

A nested-object mutation tool with 7 params and no output schema needs at minimum a statement about partial-update semantics and what a caller gets back, and the description provides neither. The preview-regeneration note is a good addition but the definition is still thin for a tool of this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3 and the schema already documents every parameter. The description's mention of text content, image URL and styling loosely maps to the nested properties object, but adds no format, precedence, or partial-update meaning beyond what the schema says.

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?

States a specific verb and resource and enumerates the property groups it affects (position, text, image URL, styling), which is enough to distinguish it from create_layer and get_layer. The one ambiguity is 'position', which the schema splits into x/y coordinates and a z-order field, and the description doesn't disambiguate.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus siblings, no statement of prerequisites, and crucially no statement of whether this is a partial patch (omitted properties preserved) or a replacement. An agent must infer call semantics from the schema alone.

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

All Layerre 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