Skip to main content
Glama

Report Publishing

report_publishing
Read-only

Check a report's publishing state: auto/manual mode, published revision, unpublished draft changes, and the pages viewers currently see. Read-only.

Instructions

Publishing state: auto/manual, published revision, whether the draft has unpublished changes and which pages viewers currently see. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "report_publishing"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this a safe read, and the trailing 'Read-only' merely repeats it. The description does add some behavioral value by naming which publishing facts are surfaced, but it says nothing about scoping, freshness, or default behavior when no report_id is supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and free of padding, but it is a sentence fragment with no leading verb, and the most important framing — that this is a read of publishing status — is implied rather than stated up front.

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 the description is not obligated to explain return values, yet it spends nearly its entire text doing exactly that. The things actually missing for correct invocation — the role of report_id and how this differs from report_publishing_mode — are absent.

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% for the single parameter report_id, and the description never mentions it at all. With low coverage, the description should have explained what report_id identifies and what happens when it is omitted (the schema defaults it to null), but it does not.

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 enumerates the fields returned (auto/manual mode, published revision, unpublished-change flag, visible pages), which implies a read of publishing state, but it never supplies a verb or a direct statement of what the tool does. It also does not differentiate itself from the sibling report_publishing_mode, which plausibly overlaps on the same subject area.

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 exclusions, and no pointer to alternatives such as report_publishing_mode for changing mode or report_audit for auditing. The agent must infer the call site from the tool name alone.

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