Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Count Schemas

count_schemas
Read-onlyIdempotent

Count the number of schemas in a specified Kafka Schema Registry context or registry to quickly assess schema inventory.

Instructions

Count the number of schemas in a context or registry.

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": "count_schemas"
  }
}

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.1/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 and the description adds the filtering dimension (context vs registry). However, it does not clarify what is actually counted (all subjects in the context? latest versions only?) or which registry is used when both parameters are omitted, which is the key behavioral ambiguity for a counting tool.

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 twelve-word sentence with the verb and scope front-loaded and no filler. Nothing could be removed without losing information.

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?

With no output schema, the description should at least establish that the return is a numeric count and what the null-default behavior is; the count nature is implied but the scoping defaults are not. For a simple two-optional-parameter read tool this is minimally adequate but leaves a real gap.

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%: neither 'context' nor 'registry' is documented in the input schema, and the description only names them in passing. It does not explain preconditions, defaults when null, or whether both can be supplied together, so it falls well short of compensating for the coverage gap.

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 gives a specific verb ('Count') and resource ('schemas') plus the scoping dimension ('in a context or registry'), so an agent can tell it counts schemas rather than contexts or versions, which are the closest siblings. It stops short of explicitly naming how it differs from count_schema_versions or count_contexts, but the resource 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of when not to use it, and no mention of what happens when neither context nor registry is supplied (both default to null and are not required). The agent must infer from the name alone whether this is the right counting tool.

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