Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Get storage stats

openpanel_get_storage_stats
Read-only

Retrieve storage usage statistics for stored events in ClickHouse by site and project ID. Use it to monitor how much event data a specific project consumes.

Instructions

[UNIFIED] Get storage usage statistics (events stored in ClickHouse).

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>",
      "project_id": "<project_id>"
    },
    "name": "openpanel_get_storage_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/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. The description contributes the extra fact that the measured data is events held in ClickHouse, which tells the agent what the numbers represent, but it says nothing about freshness, aggregation, cost/latency, or whether the response is a snapshot.

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?

A single compact sentence with the core operation front-loaded. The only waste is the bracketed '[UNIFIED]' prefix, which conveys no actionable information to an agent.

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?

This is a low-complexity read tool with no output schema, so the description needn't explain return values, and the annotation covers safety. However, two required, undocumented identifiers leave a real gap that a slightly longer description could have closed.

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% and both parameters (site, project_id) are bare strings with no documentation, yet the description adds no meaning about what 'site' identifies or how project_id relates to it. With the schema doing nothing and the description not compensating, an agent must guess at identifier formats.

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 pairs a specific verb ('Get') with a specific resource ('storage usage statistics') and clarifies in parentheses that it concerns events stored in ClickHouse, which scopes 'storage' beyond a vague reading. It stops short of differentiating itself from nearby siblings such as openpanel_get_usage_stats, and the '[UNIFIED]' tag is unexplained jargon that adds no discriminating information.

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 mention of alternatives (e.g., usage stats vs. realtime stats vs. storage stats), and no stated preconditions beyond the required identifiers. An agent must infer from the name alone when this tool is the right choice.

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