AKHQ MCP Server

get_schemas

Read-onlyIdempotent

Retrieve all schemas from the Kafka schema registry for a specified cluster. Filter by search term and control pagination using page and perPage parameters.

Instructions

List all schemas in the schema registry

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

Input Schema

Name	Required	Description
`page`	No
`search`	No
`cluster`	Yes	Cluster name
`perPage`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds little behavioral context beyond the act of listing, but does not contradict the annotations.

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?

The description is a single, front-loaded sentence with no filler or redundant elaboration. It communicates the core operation efficiently.

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?

With no output schema and multiple undocumented parameters, the description is insufficiently complete. It does not explain pagination, search behavior, or what the response contains, so an agent may not know how to correctly pass optional parameters or interpret the result.

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 description coverage is only 25%, with only 'cluster' documented in the input schema. The description does not compensate for the undocumented 'page', 'search', and 'perPage' parameters at all, leaving their meaning and usage entirely unclear.

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 clearly states the action ('List'), the resource ('schemas'), and the scope ('schema registry'). It does not explicitly differentiate from related tools like get_schema_by_subject or get_schema_versions, but 'all schemas' conveys a broad listing operation.

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 on when to use this tool versus alternative schema-related tools such as get_schema_by_subject or get_schema_versions. The intended use is only implied by 'List all schemas', with no explicit conditions or exclusions.

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

Deploy Server