Skip to main content
Glama

move_panels

Change the layout of one or more panels in a single report version without touching queries or presentation. Use when rearranging a dashboard.

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": {
      "reportId": "<reportId>",
      "moves": "<moves>"
    },
    "name": "move_panels"
  }
}

Input Schema

NameRequiredDescriptionDefault
movesYes
reportIdYesReport id
expectedVersionNoThe report `version` your edit is based on, from get_report or the last save. The save is rejected if the report changed since. Omit to apply your change to the latest version.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already supplied. The description adds genuinely useful scope information — that queries and presentation are untouched — but says nothing about version-conflict rejection or what permissions are needed for a mutation on a report version.

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 with no filler: the operation and its scope boundary come first, followed by the selection cue. Nothing is redundant or buried.

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 non-destructive layout mutation with no output schema and a well-documented schema, the description covers the essential scope question (layout only, not queries/presentation). Only concurrency and permission behavior are left unaddressed, and those are partly handled by the schema.

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 67%, and the description adds no parameter-level detail beyond the schema. The most consequential parameter, expectedVersion, is fully explained inside the schema itself, so the description's lack of coverage is tolerable but adds no extra meaning.

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 gives a specific verb and resource ('Change the layout of one or more panels in a single report version') and bounds the scope by excluding queries and presentation, which separates it from a general report-editing tool. It falls short of naming a sibling such as add_panel, so differentiation is inferred rather than stated.

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?

'Use when rearranging a dashboard' supplies a clear trigger condition for selecting this tool. It does not state when not to use it or point to an alternative for adding/removing panels, so the guidance is positive-only.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources