Skip to main content
Glama

create_report

Create a workspace report from a title, defaultRangeDays and panels. A report may start with no panels; viewers don't see it until it has one. Each panel needs a unique id, layout, presentation fields, and a query ES module. Panel type schemas come from list_panel_types. Use when building an ops dashboard such as a weekly 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": {
      "title": "<title>",
      "defaultRangeDays": "<defaultRangeDays>",
      "panels": "<panels>"
    },
    "name": "create_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
panelsYes
defaultRangeDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuine behavior the agent could not infer, namely that a report may be created empty and stays invisible to viewers until a panel exists, and that panel queries are ES modules. It does not disclose permission requirements, whether creation is reversible/undeletable, or what the response contains.

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 create action and its inputs, then the visibility rule, then the panel requirements and the helper tool. Every sentence carries information; nothing is repeated from the schema.

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?

For a tool with a deep anyOf panel schema, 0% schema description coverage, and no output schema, the description is only partially complete. It omits the meaning of defaultRangeDays, the layout grid semantics, and any statement about what is returned (e.g. the new report id) or what happens on duplicate panel ids.

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 description coverage is 0%, so the description carries the full burden. It does define panel requirements (unique id, layout, presentation fields, query ES module) and points to list_panel_types, but it never explains what defaultRangeDays controls, that layout is a 12-column grid, or the 24-panel cap, leaving most of a large nested schema undocumented.

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 ("Create a workspace report") and enumerates the three inputs it consumes, so the agent knows exactly what operation this performs. It does not explicitly contrast itself with the sibling add_panel or update_report, leaving the create-vs-extend boundary to inference.

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 a concrete usage context ("Use when building an ops dashboard such as a weekly report") and routes the agent to list_panel_types for panel type schemas, which is real when-to-use guidance. It stops short of stating when not to use it, e.g. that existing reports should be modified via update_report or add_panel rather than recreated.

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