Skip to main content
Glama

update_report

Replace fields on an existing report. Pass id plus any of title, defaultRangeDays or panels; omitted fields are kept. panels replaces the full panel list when provided. Use when reshaping a dashboard in one save.

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": "update_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReport id
titleNoReport title
panelsNo
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.
defaultRangeDaysNoRolling window in days when the URL has no range

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only mark it as non-read-only and non-destructive; the description usefully discloses merge semantics ('omitted fields are kept') and that panels wholesale-replaces the panel list, which is the main data-loss risk. It omits two behavioral points that matter for an update: the expectedVersion concurrency behavior and the fact that a stale-version save is rejected, which are only in the schema. The core mutation traits are disclosed but not completely.

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?

Three sentences, front-loaded with the core action, then edit semantics, then the usage trigger. 'Use when reshaping a dashboard in one save' is slightly promotional phrasing but still communicates a real condition.

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 5-parameter update tool with a rich nested panels schema, it covers the merge/replace semantics well and the schema documents expectedVersion thoroughly. What is missing is guidance on concurrency: the description never tells an agent to read a version first or that a save can be rejected. That matters when safe editing is the goal, so the definition is adequate but not complete.

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 roughly 80%, so the baseline is 3, and the description adds real meaning beyond the schema: default-field preservation and full-list replacement for panels. It enumerates id/title/defaultRangeDays/panels but silently skips expectedVersion, so the concurrency parameter is left only to the schema.

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 fields on an existing report') and names the exact fields it can modify, which distinguishes it from create_report and get_report. It stops short of explicitly contrasting with update_panel, but the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when reshaping a dashboard in one save' gives a positive condition for choosing this over per-field edits, which is useful. There is no exclusion guidance, such as when it is preferable to edit a single panel instead, and no prerequisites are stated.

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