Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Count Schema Versions

count_schema_versions
Read-onlyIdempotent

Count how many versions exist for a specific schema subject in Kafka Schema Registry, so you can verify schema history before changes or migrations.

Instructions

Count the number of versions for a specific schema.

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": {
      "subject": "<subject>"
    },
    "name": "count_schema_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
subjectYes
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • removedInput schema / properties / subject / title
      Removed value: -"Subject"
  2. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/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 known. Beyond that the description adds nothing: it does not say whether an unknown subject errors or returns 0, whether the count spans contexts or registries, or what form the returned count takes.

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?

A single front-loaded sentence with no filler; the verb and result are stated immediately. It is efficient but so short that the brevity comes at the cost of any useful detail.

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, undocumented parameters, and only read-only annotations, the description should tell the agent what a count means here (per-subject, per-context?). It leaves the scoping of the count and the behavior for a missing subject entirely unstated.

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% across three parameters, so the description must carry the burden and does not. It never explains the 'subject' parameter's format or the roles of the optional 'context' and 'registry' parameters, which materially change the scope of the count.

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?

States a specific verb+resource: counts versions of a schema. An agent can distinguish it from the listing sibling get_schema_versions by the word 'count'. However, it says 'specific schema' while the required parameter is named 'subject', a terminology mismatch that leaves slight ambiguity about what is being counted.

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 when-to-use or when-not-to-use guidance and no mention of alternatives. The existence of a sibling named get_schema_versions implies the count/list split, but the description never states 'use this instead of fetching the full list when you only need the total' or any precondition.

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