Skip to main content
Glama

Components Layers

components_layers
Destructive

Reorder the stacking of 1–100 top-level components on an ungrouped static page by bringing them to front/back or moving them forward/backward while preserving relative order and existing payloads.

Instructions

Change stacking of 1–100 top-level components on one ungrouped static page.

Actions: bring_to_front, send_to_back, bring_forward, send_backward. Preserves relative order inside selected and unselected subsets, independent of input ID order. At the requested boundary returns unchanged without a write. Component payloads, child order, geometry and conditions are preserved. Preview lists full before/after order back-to-front. report_refresh first, page_get fingerprint, versioned write/read-back/journal/operation_restore. Grouped and responsive pages and report-level layers need separate support.

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": {
      "page_id": "<page_id>",
      "component_ids": "<component_ids>",
      "action": "<action>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "components_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
dry_runNo
page_idYes
report_idNo
component_idsYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare this is a destructive, non-read-only mutation, but the description adds substantial behavior beyond them: relative order is preserved inside selected and unselected subsets, ID input order does not matter, a no-op returns unchanged at the boundary without writing, payloads/child order/geometry/conditions are preserved, and preview returns full before/after order. It also describes the surrounding safety workflow: refresh first, fingerprint check, versioned write, read-back, journal, and operation restore.

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?

The description is front-loaded with purpose and action list, then packs behavioral guarantees and workflow dependencies into a few dense sentences. It is efficient with little waste, though the final workflow clause is tersely compressed and could be slightly harder to parse.

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?

For a complex destructive mutation with six parameters and an output schema, the description covers scope, ordering semantics, preservation guarantees, no-op behavior, preview behavior, fingerprint safety, and restore workflow. The main remaining gaps are explicit dry_run semantics and report_id usage, but the output schema reduces the need to explain return values.

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?

With 0% schema description coverage, the description does meaningful work: it explains the four action values, constrains component_ids to 1–100 top-level components, notes order independence from input ID order, and ties expected_fingerprint to page_get. It implies preview mode through the preview sentence but does not explicitly define dry_run or explain when report_id should be supplied, leaving some parameter meaning to inference.

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: changing stacking of 1–100 top-level components on one ungrouped static page. It enumerates the four actions and explicitly bounds scope by noting that grouped pages, responsive pages, and report-level layers need separate support, which lets an agent distinguish this from broader arrangement tools.

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?

The description gives clear context for when this tool applies: ungrouped static pages, top-level components, and only the four listed stacking actions. It also signals when not to use it by saying grouped/responsive pages and report-level layers need separate support, though it does not explicitly name the alternative sibling tool to use instead.

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