Skip to main content
Glama
Sign In
GreptimeDB MCP Server

GreptimeDB MCP Server

Official
by GreptimeTeam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_dashboard

Create or update Perses dashboard definitions in GreptimeDB to visualize and monitor database metrics.

Instructions

Create or update a Perses dashboard definition in GreptimeDB.

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": {
      "name": "<name>",
      "definition": "<definition>"
    },
    "name": "create_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
definitionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states 'Create or update'. It does not explain whether updates overwrite existing definitions, what happens on duplicate names, or any permission requirements. The lack of detail leaves significant ambiguity for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is too brief to convey necessary detail. It achieves conciseness at the expense of completeness, which is not ideal.

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?

Given the tool has an output schema (not shown), the description does not need to explain return values, but it lacks essential context about behavior (e.g., idempotency, if it's a full replacement). The parameter descriptions are absent, and the complexity of 'create or update' is not addressed, making the description incomplete.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no meaning to the two parameters (name, definition). Both are just listed as string types without any explanation of their purpose, format, or constraints. This is a crucial gap for a tool with only two required parameters.

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 the verb 'Create or update' and specifies the resource ('Perses dashboard definition') and the context ('in GreptimeDB'), making the function clear. It distinguishes from sibling tools like delete_dashboard and list_dashboards, but the dual action (create/update) slightly reduces specificity.

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?

No guidance is provided on when to use this tool versus alternatives, nor are there any exclusions or prerequisites mentioned. The agent must infer usage from the tool name and context.

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