Skip to main content
Glama

Load a layer set

get_layer_set

Reopens a split-into-layers image result after chat reload by retrieving its layer set using any image ID in the set.

Instructions

Used by the image card to reopen a split-into-layers result after the chat is reloaded. Not useful to call directly.

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": {
      "id": "<id>"
    },
    "name": "get_layer_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of any image in the set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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, and it does disclose that this is an internal UI-support call invoked by the image card after a chat reload. It doesn't state whether the operation is read-only, whether it has side effects (e.g., caching or restoring state), or what the response contains.

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, zero filler, with the audience and the cautions front-loaded. Nothing could be removed without losing meaning.

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?

For a simple one-param tool with no output schema, the definition covers who calls it and whether an agent should, but omits what the call yields (layer set contents, identifiers), which matters since no output schema documents the return shape. Adequate but with a clear gap.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that it is 'the id of any image in the set.' The description adds nothing contradictory and requires no compensation, meeting the baseline for a one-parameter tool.

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

Purpose3/5

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

The description says it reopens a 'split-into-layers result,' which adds some specificity about the resource (a layer set tied to a prior image split). But it doesn't describe what the call actually returns or how it differs from siblings such as get_generated_image, leaving the operation only loosely characterized beyond the name and title.

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?

It explicitly states a when-NOT-to-use condition: 'Not useful to call directly,' which is exactly the kind of exclusion an agent needs to avoid wasting a call. It stops short of naming what to use instead for direct layer access, but the negative guidance is unambiguous.

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