Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

List Subjects

list_subjects
Read-onlyIdempotent

List all Kafka Schema Registry subjects, optionally filtered by context, to discover available schemas for validation or selection.

Instructions

List all subjects, optionally filtered by context.

NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/subjects' resource instead for better performance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_subjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context / title
      Removed value: -"Context"
    • removedInput schema / properties / registry / title
      Removed value: -"Registry"
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description usefully adds the backward-compatibility/deprecation status and a performance comparison against the resource alternative, but says nothing about result shape, ordering, pagination, or what an empty context filter returns.

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

Conciseness4/5

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

Two sentences, front-loaded with the action statement and followed by a clearly marked NOTE. Both sentences earn their place; only the emphasis formatting is slightly heavy for the content.

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 zero-required-param read tool with no output schema this is close to sufficient, but the undocumented 'registry' parameter and absence of any hint about the returned subject list leave real gaps.

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%, so the description must carry parameter meaning. It only explains 'context' as an optional filter and never mentions the 'registry' parameter at all, leaving one of two parameters undocumented in both schema and description.

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?

'List all subjects, optionally filtered by context' states a specific verb and resource with clear scope. It does not explicitly distinguish itself from siblings such as get_subjects_by_schema_id or list_contexts, but the core purpose is unambiguous.

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 condition (optionally filtered by context) and a clear routing recommendation: prefer the 'registry://{name}/subjects' resource for better performance. It does not state when the tool is still the right choice (e.g., legacy clients) or when to pick a sibling tool, but the primary guidance is explicit.

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