Skip to main content
Glama
Sign In
AKHQ MCP Server

AKHQ MCP Server

by seb-noirot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_ksqldb_queries

Read-onlyIdempotent

List all running ksqlDB queries for a specified cluster and ksqlDB instance to identify active streams and troubleshoot processing issues.

Instructions

List all ksqlDB queries

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": {
      "cluster": "<cluster>",
      "ksqldb": "<ksqldb>"
    },
    "name": "get_ksqldb_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
ksqldbYesksqlDB cluster name
clusterYesCluster name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, which the description matches. The description adds no further behavioral context such as pagination, response shape, or whether the listing is scoped to the provided cluster.

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?

A single sentence with no filler and the key action front-loaded. It is appropriately concise for a simple read-only list operation.

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 simple listing tool, the description is mostly adequate given the schema and annotations. However, with no output schema, it does not describe what a returned ksqlDB query looks like or clarify whether the list is scoped to the required cluster/ksqldb parameters.

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 100%, and both parameters have straightforward names and descriptions. The tool description itself adds no additional parameter-level meaning, so the baseline score of 3 applies.

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 states a specific verb ('List') and resource ('ksqlDB queries'), with an explicit 'all' scope. It doesn't explicitly contrast with sibling tools, but the resource type is distinct from get_ksqldb_streams and get_ksqldb_tables.

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 guidance about when to use this tool versus alternatives such as get_ksqldb_streams, get_ksqldb_tables, or put_ksqldb_query. The intended usage must be inferred entirely from the tool name and the sibling list.

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