Skip to main content
Glama

add_panel

Append one panel to a report without resending the others. The panel needs a unique id, layout, presentation fields, and a query. Saves one report version (max 24 panels). Use when extending an existing 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>",
      "panel": "<panel>"
    },
    "name": "add_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
panelYes
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

A4.4/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive write; the description adds genuinely useful behavior beyond that: each call saves one report version, panels are appended rather than replaced, and there is a hard ceiling of 24 panels per report. It doesn't say what error occurs at the limit or what is returned on success, keeping it below a 5.

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, front-loaded with the action and its incremental-save distinction, then the panel requirements, then the usage trigger. Nothing is redundant or padded.

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 tool with a four-variant anyOf panel schema and no output schema, the description covers the essentials an agent needs: required panel shape, uniqueness of id, version semantics at a high level, and the 24-panel cap. It could go further by stating what the save returns (e.g. the new version) since expectedVersion chaining depends on it.

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?

Beyond the 67%-covered schema, the description clarifies that the panel's id must be unique (schema only enforces minLength) and enumerates the required makeup of a panel: id, layout, presentation fields, and query. It leaves the expectedVersion optimistic-concurrency parameter to the schema, which already documents it well.

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 (append) and resource (one panel to a report), and clarifies the incremental save semantic with "without resending the others," which clearly separates it from an update_panel or full report save. An agent can pick this over siblings without opening the 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?

"Use when extending an existing dashboard" gives a clear positive trigger. It does not name exclusion cases (e.g. use update_panel to modify an existing panel, remove_panel to delete), so the when-not side is left to inference.

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