Skip to main content
Glama
Sign In
MCP Kafka Schema Reg

MCP Kafka Schema Reg

by aywengo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Available Resources

list_available_resources
Read-onlyIdempotent

Lists all available MCP resources and their usage patterns so you can discover what data and operations the Kafka Schema Registry server exposes.

Instructions

List all available MCP resources and their usage patterns.

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_available_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.0.0

TDQS

B3.3/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 adds only that results include "usage patterns," without saying what those look like, whether the list is paginated, or whether it is scoped to a server/session.

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 only weakness is that the second half ("usage patterns") is under-defined rather than wasteful.

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 zero-argument, read-only discovery tool with no output schema, the description should clarify what "resources" and "usage patterns" resolve to, since the return content is otherwise unspecified. It is adequate to trigger a call but leaves the agent guessing about output shape.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to supply. Baseline of 4 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?

States a specific verb and resource ("List all available MCP resources"), which separates it from sibling listers like list_contexts or list_registries. The trailing phrase "and their usage patterns" is vague and slightly muddies what the resource actually is.

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 guidance on when to call this versus siblings such as list_contexts or list_registries, and no prerequisites or exclusions are mentioned. The agent must infer that this is the discovery entry point.

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

Deploy Server

Other Tools