Skip to main content
Glama

Report Theme Copy

report_theme_copy
Destructive

Copies another report's custom theme onto this report so imported pages match the source exactly. Reads the source only; preview, apply, and restore safely.

Instructions

Give this report the theme of another report (its custom theme, made active), e.g. after pages_import so the copied pages look exactly like the source. Report-wide: every page here takes it. Open both reports with report_open; the source is only read. Fingerprint from report_content_get. Journalled, restorable.

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": {
      "source_report_id": "<source_report_id>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "report_theme_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
source_report_idYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: it discloses the blast radius ("Report-wide: every page here takes it"), that the operation is safe on the other side ("the source is only read"), that it is reversible ("Journalled, restorable") despite being destructive, and that a fingerprint concurrency guard is required. That is exactly the risk information an agent needs before performing a destructive mutation.

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?

Front-loads the core action in the first sentence and stacks scope, preconditions, and risk in short clauses with no filler. The final fragment "Fingerprint from report_content_get." is telegraphic and reads as a note rather than a sentence, which costs a little clarity.

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 destructive, report-wide mutation with an output schema and a documented journal/restore path, the definition covers purpose, scope, prerequisites, and reversibility well. The remaining hole is operational: dry_run defaults to true and is never mentioned, so an agent may think it has already applied the theme when it has only staged it.

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 0%, so the description must carry the parameter burden, and it only partially does: it clarifies that source_report_id is read-only and that expected_fingerprint comes from report_content_get. It never mentions dry_run (which defaults to true and cheapens the call) nor explains that report_id selects the target report and what a null value means, so two of four parameters remain unexplained.

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 ("Give this report the theme of another report") and pins the exact semantics in parentheses: it copies the source's *custom* theme and makes it active. The scope is explicit ("Report-wide: every page here takes it"), so an agent can distinguish this from create-a-theme-from-scratch tools like theme_from_image without opening a 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?

Gives a concrete trigger ("e.g. after pages_import so the copied pages look exactly like the source") and a prerequisite ("Open both reports with report_open"), which tells the agent exactly when in a workflow to call it. It does not, however, name an alternative or state when *not* to use it (e.g. when themes are template/global rather than custom), leaving a small gap.

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