Skip to main content
Glama

Report Refresh

report_refresh
Read-only

Reload a report draft in the MCP tab, optionally opening a specific page, while preserving unsaved editor changes through autosave. Use it after external edits or before page duplication.

Instructions

Reload the report draft in the MCP tab, optionally on another page.

Tools already reload after writes and when the model is stale; use this to open a specific page (e.g. before page_duplicate) or after edits made outside the MCP. Never discards unsaved editor changes: an open editor is autosaved first.

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_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idNo
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.7/5.0
Behavior1/5

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

The description adds useful behavior about automatic reload triggers and not discarding unsaved changes. However, 'an open editor is autosaved first' discloses a write side effect, which conflicts with the readOnlyHint=true annotation.

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?

Two short paragraphs, front-loaded with the action and then the usage guidance; every sentence adds routing or safety information. There is no repetitive or filler text.

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 simple two-optional-parameter refresh tool with an output schema, the description covers purpose, usage, and the key autosave safety trait. The main remaining gap is parameter meaning, especially report_id.

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%, so the description must explain page_id and report_id. It only hints that the tool can act 'on another page' and says nothing about report_id, its default, or identifier format.

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?

The first sentence gives a specific verb ('Reload') and resource ('the report draft in the MCP tab') and adds optional page scope. It also distinguishes this explicit refresh from the automatic reloads that happen after writes or staleness.

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

Usage Guidelines5/5

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

It explicitly states when not to use it (tools already reload after writes and when the model is stale) and when to use it (to open a specific page, e.g. before page_duplicate, or after edits made outside the MCP). This is clear when/when-not routing with a concrete example.

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