docs-mcp

List Connect Components

list_connect_components

Read-only

List or search Redpanda Connect components by type, keyword (matched against name, categories, and summary), status, or Redpanda Cloud support. Returns compact rows with docs URLs. Name matches rank above category and summary matches. Use it to discover what exists (for example every 'Services' input, or every output available in Cloud) before get_connect_component. total=0 means nothing matches.

Input Schema

Name	Required	Description
`type`	No	Only components of this type. Omit for all types.
`limit`	No	Maximum rows to return (default 25, max 100).
`query`	No	Keyword, e.g. 'kafka', 'postgres', 'aws'.
`status`	No	Only components with this status.
`context`	No	Optional. In one concise sentence (third person), describe what the user is trying to accomplish with this request. Do not include credentials, tokens, personal data, or verbatim secrets.
`session_goal`	No	Optional. In one concise sentence (third person), the overall goal of this session: what the user is trying to get done, not just this call. Send the same goal on every call in the session, and update it only if the goal changes. Do not include credentials, tokens, personal data, or verbatim secrets.
`cloud_supported`	No	true: only components available in Redpanda Cloud; false: only self-managed-only ones.

Output Schema

Name	Required	Description
`error`	No	Set when the call was not answered: 'anonymous_quota_exhausted' or 'data_unavailable'.
`limit`	No	Quota refusal only.
`total`	No	Absent only when `error` is set.
`dataset`	No
`message`	No
`returned`	No
`resets_at`	No	Quota refusal only.
`components`	No
`sign_in_url`	No	Quota refusal only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / session_goal

Added value: +{
+  "description": "Optional. In one concise sentence (third person), the overall goal of this session: what the user is trying to get done, not just this call. Send the same goal on every call in the session, and update it only if the goal changes. Do not include credentials, tokens, personal data, or verbatim secrets.",
+  "type": "string"
+}

AddedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

While the annotations provide a strong safety profile (readOnly, non-destructive), the description adds critical behavioral context beyond structured fields: it discloses the return format ('compact rows with docs URLs'), search ranking logic ('Name matches rank above category and summary matches'), and how to interpret an empty result ('total=0 means nothing matches').

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?

The description is highly efficient and front-loaded. Every sentence provides necessary information—purpose, search behavior, return format, usage guidance, and edge-case handling—without any fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool (7 optional parameters) and the existence of an output schema, the description is complete. It equips the agent with everything needed to call the tool correctly and interpret both its results and its empty state.

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?

Schema coverage is 100%, establishing a baseline of 3, but the description adds valuable semantic context. It clarifies exactly what the keyword query searches against ('matched against name, categories, and summary') and explains the ranking behavior, which is not captured in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List or search') and resource ('Redpanda Connect components'), along with the filtering dimensions. It distinguishes itself from the detail-oriented sibling tool by explicitly positioning itself as a discovery mechanism for use 'before get_connect_component.'

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance ('Use it to discover what exists... before get_connect_component') and gives concrete examples of use cases ('every Services input, or every output available in Cloud'). The alternative tool is explicitly named.

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

All docs-mcp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.