Skip to main content
Glama

preview_panel

Run a draft panel query against this workspace's real data for a date range without saving. Returns { status: "ok", data } or { status: "error", details }. from/to are inclusive YYYY-MM-DD, at most 366 days apart. Use when iterating on a panel before create_report or update_report.

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": {
      "panel": "<panel>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "preview_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRange end, YYYY-MM-DD
fromYesRange start, YYYY-MM-DD
panelYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=false and openWorldHint=false, and the description usefully adds that nothing is persisted ('without saving') and that it executes against real workspace data, plus its return shape. The readOnlyHint=false is not contradicted by the description but is also never explained, and there is no mention of cost, rate limits, or query permission failures despite real data execution.

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?

Four short sentences, front-loaded with the action and its no-save guarantee, followed by return shape, constraints, and usage routing. No filler and no repetition of the tool title.

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?

There is no output schema, but the description compensates by describing both the ok and error response envelopes. Combined with the inclusive-range and 366-day constraints, an agent has enough to call it correctly; only edge cases (partial series failures, whether the panel definition is validated) remain unstated.

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 coverage is 67%, so the schema documents the parameters reasonably well. The description adds genuine semantics for `from`/`to` (inclusive, YYYY-MM-DD format, 366-day maximum span) that the schema only partially conveys, but says nothing about `panel` beyond the implicit 'draft panel', which is the most complex parameter.

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?

The description uses a specific verb and resource ('Run a draft panel query') and states the essential scope ('against this workspace's real data', 'without saving'), which tells an agent this is an ad-hoc evaluation, not a fetch of a stored panel. It does not explicitly distinguish itself from get_panel_data or list_panel_types, so the sibling differentiation is partial rather than complete.

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?

It gives clear when-to-use guidance: 'Use when iterating on a panel before create_report or update_report', naming the downstream tools an agent would otherwise reach for. There is no explicit when-not-to-use condition (e.g., when to call get_panel_data instead), which keeps it below a 5.

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