Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Schema By Id

get_schema_by_id
Read-onlyIdempotent

Fetch a Kafka Schema Registry schema by its globally unique ID to resolve schema details; include an optional registry name when using multiple registries.

Instructions

Get a schema by its globally unique ID.

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": {
      "schema_id": "<schema_id>"
    },
    "name": "get_schema_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
registryNoOptional registry name (ignored in single-registry mode)
schema_idYesThe globally unique schema ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / registry / description
      Added value: +"Optional registry name (ignored in single-registry mode)"
    • removedInput schema / properties / registry / title
      Removed value: -"Registry"
    • addedInput schema / properties / schema_id / description
      Added value: +"The globally unique schema ID"
    • removedInput schema / properties / schema_id / title
      Removed value: -"Schema Id"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds essentially nothing beyond that — no statement about what is returned (full schema text? metadata?), no behavior when the ID is unknown, and no note about the single-registry mode that the registry parameter hints at.

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?

One short sentence with zero filler, front-loading the verb and resource. It is efficient but borders on under-specification rather than being tightly informative.

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 read-only lookup with full schema coverage and annotations, the essentials are present, so an agent can call it. Still missing is any indication of the return payload or how it differs from the similarly named schema-retrieval siblings, which matters given how many of them exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the note that registry is ignored in single-registry mode, so the schema carries the parameter burden. The description only echoes the schema_id semantics ("globally unique ID") and adds no format, range, or lookup behavior details. Baseline 3 applies.

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 states a specific verb and resource ("Get a schema") and narrows the lookup key to a globally unique ID, which is meaningful in a registry context. It does not, however, distinguish itself from siblings such as get_schema or get_schema_versions, so an agent must infer the difference from the names alone.

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: nothing says to prefer this over get_schema, get_schema_versions, or get_subjects_by_schema_id, nor what prerequisites exist (e.g., that the ID must already be known). The agent is left to infer selection from the tool name.

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