Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Export chart data

openpanel_export_chart_data
Read-only

Export aggregated chart data as time series with event breakdowns, date ranges, and interval options for analytics reporting.

Instructions

[UNIFIED] Export aggregated chart data with time series and breakdowns. Requires 'read' or 'root' mode client.

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": {
      "site": "<site>",
      "events": "<events>"
    },
    "name": "openpanel_export_chart_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
eventsYes
intervalNoday
previousNo
breakdownsNo
date_rangeNo30d
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description adds genuine value by disclosing the client-mode authorization requirement. However, nothing is said about aggregation semantics (what interval bucketing means, what 'previous' comparison returns), result size limits, or export format, which matter for a data-export tool.

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?

Two sentences, front-loaded with the core action and followed by the access constraint, with no filler. The '[UNIFIED]' tag is noise that does not help an agent decide anything, but the rest is tight.

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

Completeness2/5

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

With 7 undocumented parameters, no output schema, and moderate complexity, the definition leaves too much unresolved: the shape of the returned aggregate, the date-range format, and how breakdowns interact with events are all unstated. The authorization note is useful but insufficient to make the tool reliably callable.

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 7 parameters, so the description carries the full burden and largely fails. It only hints that 'interval' and 'breakdowns' relate to time series and breakdowns; 'site', 'events', 'date_range' (default '30d'), 'previous', and 'project_id' receive no explanation of expected syntax or effect.

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 names a specific verb and resource: 'Export aggregated chart data with time series and breakdowns', which tells an agent this returns pre-aggregated analytics rather than raw events. It does not, however, distinguish itself from sibling readers such as openpanel_get_overview_report, openpanel_get_device_data or openpanel_export_events, so the boundary must be inferred from the name.

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

Usage Guidelines3/5

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

The only guidance is a prerequisite: a 'read' or 'root' mode client is required. There is no statement of when to prefer this tool over the many sibling OpenPanel analytics tools, and no mention of failure behavior when the client mode is insufficient.

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