Skip to main content
Glama
Sign In

Layerre

by com.layerre
OverviewDiscussionsAdmin

Create layer

layerre_create_layer

Create a new layer (text or image) for a template. Layer type is inferred from properties if not specified.

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>"
    },
    "name": "layerre_create_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoX position in pixels (default: 0)
yNoY position in pixels (default: 0)
nameNoLayer name (default: "New Layer")
layer_typeNoLayer type (inferred from properties if not provided)
propertiesNoLayer properties (text, img_url, styling, etc.)
template_idYesThe UUID of the template to add the layer to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds one useful behavioral rule (layer type is inferred from properties if not specified), but says nothing about what happens on invalid template_id, how existing layers/variants are affected, or whether a layer id is returned.

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?

Two short sentences with the core action front-loaded and the type-inference rule following. It is efficient, though the second sentence duplicates the layer_type field description verbatim rather than adding new 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?

The input schema is rich enough to drive the call, and no output schema exists, so the description needn't enumerate returns. However, for a creation tool with a complex nested properties object, it omits what an agent most needs: confirmation that template_id must exist, and what identifier comes back to use with layerre_update_layer or layerre_get_layer.

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 schema already documents all six top-level parameters and their defaults. The description only restates the layer_type inference behavior; with a large nested properties object whose ~20 sub-fields are undescribed, it adds no guidance on which properties map to text vs image layers.

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 ('Create a new layer') and scopes it ('for a template'), plus states the two supported layer kinds (text/image). It is clearly distinguishable from layerre_update_layer and layerre_create_template, though it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer you call this to add a layer to an existing template, and that layer_type can be omitted in favor of inference. There is no explicit when-to-use versus layerre_update_layer, no prerequisite that template_id must reference an existing template, and no note on limits or ordering.

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