Skip to main content
Glama

Report Publishing Mode

report_publishing_mode
Destructive

Configures report publishing to auto-publish every saved change immediately or manual mode to keep edits in a draft until published.

Instructions

File > Publishing settings: auto publishes every saved change (including the current draft, immediately); manual keeps edits in a draft until report_publish.

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": {
      "mode": "<mode>"
    },
    "name": "report_publishing_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
dry_runNo
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3/5.0
Behavior4/5

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

The annotations declare destructiveHint=true and readOnlyHint=false, and the description genuinely adds to that by spelling out the consequence: auto mode publishes every saved change including the current draft immediately, while manual holds edits until report_publish. That immediate-publish-of-current-draft warning is exactly the risk context an agent needs. It does not address the dry_run default of true, which is a notable omission for a destructive operation.

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?

A single compact sentence that front-loads the setting context and then contrasts the two modes. The 'File > Publishing settings:' prefix is slightly UI-centric but orients the reader quickly; there is little waste.

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?

An output schema exists, so return values need no explanation. However, for a destructive, default-dry-run configuration tool, the description omits any mention of dry_run and report_id, and never states plainly that it writes a setting rather than describing one. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate. It does well on mode, explaining both enum values and their effects, but says nothing about dry_run (defaulting to true) or report_id, leaving two of three parameters without any semantic explanation anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains what the two mode values mean ('auto publishes every saved change... manual keeps edits in a draft'), which implies this tool sets that mode. But it never states the action explicitly – 'File > Publishing settings:' is a UI location, not a verb+resource statement. An agent can infer it configures publishing behavior, but the tool's actual operation is left implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no explicit exclusion or alternative. The mention of report_publish describes a behavioral dependency in manual mode rather than routing guidance, and nothing tells the agent when to prefer one mode or when this tool should be called at all.

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