Skip to main content
Glama

get_panel_data

Read-onlyIdempotent

Get one saved panel's data for a date range (the same numbers the report page shows). from/to are inclusive YYYY-MM-DD; omit both for the report default range. Returns { status: "ok", data, range } or { status: "error" }. Use when reading metrics from an existing weekly or ops 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": {
      "reportId": "<reportId>",
      "panelId": "<panelId>"
    },
    "name": "get_panel_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end, YYYY-MM-DD
fromNoRange start, YYYY-MM-DD
panelIdYesPanel id
reportIdYesReport id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, so the safety profile is covered; the description goes further by disclosing the exact return contract (`{ status: "ok", data, range }` vs `{ status: "error" }`) in the absence of an output schema. It also explains the default-range behavior when from/to are omitted, which is real behavioral context an agent cannot get from the annotations.

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?

Three tight sentences: purpose first, parameter semantics second, return contract and usage context last. No filler or restated name, and the parenthetical about the report page earns its place by anchoring the data semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with only four documented parameters and no output schema, the description covers purpose, parameter defaults, and the success/error return shape. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so a 3 is the baseline; the description adds meaning beyond the schema by stating from/to are inclusive and that omitting both yields the report default range. That 'both-or-neither' rule is not expressed in the schema and materially affects correct invocation.

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 opens with a specific verb and resource ('Get one saved panel's data for a date range') and clarifies the semantics with 'the same numbers the report page shows,' which tells an agent exactly what comes back. It is clearly a saved-panel read, distinct from table or workspace tools, though it does not explicitly name the closest sibling (preview_panel) that an agent might confuse it with.

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?

'Use when reading metrics from an existing weekly or ops report' gives a concrete when-to-use condition tied to report context. It does not state when-not to use it or name an alternative such as preview_panel for unsaved panels, so the routing is clear but not exclusive.

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