Skip to main content
Glama
Sign In

Layerre

by com.layerre
OverviewDiscussionsAdmin

Generate variants in bulk

layerre_create_variants_bulk

Generate many variants (rendered images) from one template in a single request, e.g. one per row of data. All items share one export format. Expensive: use sparingly and keep batches small. combine_pdf merges PDF items into one multi-page PDF (Plus plan or above).

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>",
      "export_type": "<export_type>",
      "items": "<items>"
    },
    "name": "layerre_create_variants_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesVariant items to render (max 25 per call)
combine_pdfNoMerge all items into one multi-page PDF (export_type must be pdf)
export_typeYesExport format for every item in the batch
template_idYesThe UUID of the template to generate from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover the safety profile (non-readonly, non-destructive, non-idempotent). The description adds genuinely new traits: the operation is expensive, batches should be small, all items share one export format, and combine_pdf is plan-gated at Plus or above. It doesn't say whether rendering is synchronous or how outputs are returned, which is the remaining behavioral gap.

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?

Three short sentences with zero filler: what it does, the canonical use case, then the cost and plan caveats. The cost warning is placed where an agent will read it before committing to a large batch.

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?

Covers the expensive-batch and plan-gating risks that matter most for a 25-item bulk render with no output schema. What's left unsaid is the return shape (variant IDs, URLs, or inline data), which forces the agent to inspect the response rather than anticipate it.

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 coverage is 100%, so every parameter is already documented, making 3 the baseline. The description corroborates the batch/export_type relationship and adds the plan requirement for combine_pdf that the schema omits, but adds no syntax or format detail beyond that.

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?

States a specific verb and resource ('Generate many variants (rendered images) from one template in a single request') and the bulk framing plus 'single request' distinguishes it from the singular sibling layerre_create_variant. An agent can pick between the two without opening either schema.

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

Usage Guidelines4/5

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

Gives a concrete usage scenario ('e.g. one per row of data') and a cost warning ('Expensive: use sparingly and keep batches small'), which steers toward smaller batches or the single-variant sibling. It never names layerre_create_variant explicitly as the alternative for one-off renders, so the routing is implied rather than stated.

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