Skip to main content
Glama

update_panel

Replace one panel, matched by panel.id, without resending the others. Send the whole panel. Saves one report version. Use when editing a single chart or KPI.

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": "update_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.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the panel is fully replaced rather than patched ('Send the whole panel') and that the call 'Saves one report version', which tells the agent about versioning side effects. It omits what happens if panel.id does not exist and does not mention version-conflict rejection, which is the main behavioral risk for an update.

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?

Four short sentences, front-loaded with the replace/match semantics, then the payload rule, then the side effect, then the usage cue. Every sentence carries distinct information.

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?

Given a large nested panel union schema and no output schema, the description covers the three things an agent could get wrong: replacement vs merge, id-based matching, and version creation. Missing only error/edge behavior (unknown id, version conflict), which the schema partially covers via expectedVersion.

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?

Schema coverage is 67%, and the description adds genuinely non-obvious meaning: the panel object is a full replacement payload, not a partial patch, and matching is by panel.id. It says nothing about expectedVersion, leaving that to the schema's own description.

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?

States a specific verb and resource ('Replace one panel, matched by panel.id') and clarifies it is a single-panel operation that leaves siblings untouched, which implicitly separates it from add_panel/remove_panel. It never names an alternative tool, so full sibling differentiation is only inferred.

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 editing a single chart or KPI' gives a clear positive selection cue, and 'without resending the others' implies the contrasting whole-report path. No explicit when-not or named alternative (e.g., update_report) is given.

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