Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Registry Insights

get_registry_insights
Read-onlyIdempotent

Report version spread, schema types, compatibility overrides and dangling references for a registry.

Instructions

Report version spread, schema types, compatibility overrides and dangling references for a registry.

A point-in-time snapshot of registry state. Usage, consumer and historical data are not available.

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

Input Schema

NameRequiredDescriptionDefault
top_nNo
contextNo
registryNo
version_sprawl_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.2.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 safety is covered. The description adds genuine context beyond that: the result is a point-in-time snapshot rather than a live or aggregated view, and usage/consumer/historical dimensions are deliberately absent. It says nothing about cost, paging, or size limits for a report that can enumerate dangling refs.

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 short sentences, front-loaded with the reported content, then a scoping caveat. No filler, though the caveat is compressed into a single line that would benefit from being attached to a named alternative.

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 four undocumented parameters, no output schema, and only read-only/idempotent annotations, an agent cannot tell what top_n limits or what context/registry scoping does. The description names the report's contents but gives no shape, size, or parameter semantics, which is inadequate for a multi-parameter analytical tool.

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 four parameters (top_n, context, registry, version_sprawl_threshold), so the description carries the full burden and largely fails. Only faint hints appear — "for a registry" for the registry param and "version spread" for version_sprawl_threshold — while top_n and context are never explained anywhere.

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 uses a concrete verb ("Report") with an explicit list of the resources covered: version spread, schema types, compatibility overrides, and dangling references. That makes the output content distinct from a bare stats tool, though it never names a sibling to contrast with. Sibling differentiation is only implied via the exclusion of usage/consumer/historical data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The line "A point-in-time snapshot of registry state. Usage, consumer and historical data are not available" functions as a partial when-not rule, steering the agent away for usage analytics. However, it never names an alternative (e.g. get_registry_statistics) or states a positive triggering condition, so the routing is left to inference.

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