GreptimeDB MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

execute_sql

Execute a SQL query against GreptimeDB. Supports read-only queries by default, with optional write mode for destructive operations.

Instructions

Execute SQL query against GreptimeDB. Please use MySQL dialect.

Read-only by default. When the server runs with write mode enabled
(--allow-write / GREPTIMEDB_ALLOW_WRITE), destructive SQL (DDL/DML) is
also permitted.

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": {
      "query": "<query>"
    },
    "name": "execute_sql"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`query`	Yes
`format`	No	csv

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.0Jun 10, 2026

addedInput schema / properties / format

Added value: +{
+  "default": "csv",
+  "title": "Format",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 1000,
+  "title": "Limit",
+  "type": "integer"
+}

removedInput schema / properties / query / description

Removed value: -"The SQL query to execute (using MySQL dialect)"

addedInput schema / properties / query / title
```
Added value: +"Query"
```
addedInput schema / title
```
Added value: +"execute_sqlArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "execute_sqlOutput",
+  "type": "object"
+}

First observedv1.0.0Aug 18, 2025

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided. Description discloses read-only default and write mode conditions, but lacks details on error handling, transaction behavior, or performance implications.

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 short sentences, front-loaded with purpose, no fluff. Every sentence adds value.

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?

Covers main usage and permissions. Output schema exists, so return values are covered. But parameter semantics are missing; given 3 params and no description of them, completeness is moderate.

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%, but description does not explain any parameter meanings (e.g., query, format, limit). Only tool context is provided, leaving schema to carry full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'Execute' and resource 'SQL query against GreptimeDB', with specific mention of MySQL dialect. Distinguishes from sibling execute_tql.

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?

Explicitly states read-only default and conditions for enabling write mode. Does not directly compare with alternatives, but sibling names suggest distinct purposes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server