docs-mcp

Get Config Property

get_config_property

Read-only

Look up one Redpanda configuration property (cluster, broker, or topic) by exact name and return its documented type, default, description, restart and enterprise flags, Redpanda Cloud availability, related properties, and docs URL. Deterministic: it reads the generated property dataset for the requested docs version, so a property that does not exist returns found=false with close-name suggestions instead of a guess, and no LLM or search is involved. Use this before ask_redpanda_question for any question about a specific property's default, type, or availability. Pass platform='cloud' to learn whether the property is supported or editable in Redpanda Cloud.

Input Schema

Name	Required	Description
`name`	Yes	Exact property name, e.g. 'log_segment_size' or 'cleanup.policy'. Aliases are accepted.
`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.
`version`	No	Docs version as its URL spells it ('26.1'), 'current' for the latest release, or a release tag ('v26.2.4'). Omit for the latest release. An unknown value returns found=false with the list of published versions. Ignored when platform is 'cloud', which always answers from the latest release.
`platform`	No	'cloud' answers for Redpanda Cloud (Cloud availability, the Cloud docs page); 'self-managed' (the default) answers for Self-Managed Redpanda.
`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.

Output Schema

Name	Required	Description
`name`	No
`note`	No	How the version or platform was interpreted, when not literally.
`error`	No	Set when the call was not answered: 'anonymous_quota_exhausted' or 'data_unavailable'.
`found`	No	Absent only when `error` is set.
`limit`	No	Quota refusal only.
`reason`	No	Why found is false.
`dataset`	No
`message`	No
`property`	No
`resets_at`	No	Quota refusal only.
`matched_via`	No
`sign_in_url`	No	Quota refusal only.
`suggestions`	No	Close property names, when not found.
`valid_versions`	No

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.4/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world, so the safety bar is covered. The description adds genuine value beyond that: deterministic reads of a generated dataset, no LLM/search involved, and the failure mode (found=false with close-name suggestions rather than a guess). It does not mention pagination or output shape, but the output schema exists to cover that.

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?

Front-loaded with verb+resource+return payload, then determinism, then routing advice. Dense but every clause carries information; the 'no LLM or search is involved' phrasing is slightly redundant with 'deterministic' but earns its place as a disambiguation signal.

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?

For a single-lookup read tool with an output schema and full parameter documentation, nothing an agent needs is missing: what it does, what it returns, what happens on a miss, version/platform scoping, and which sibling to prefer are all present.

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 coverage is 100%, so all five parameters are already documented in structured form. The description reinforces only two things the schema already states – that 'name' must be exact and that platform='cloud' answers Cloud availability – and adds no new syntax or format detail. Baseline 3 applies.

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 (look up), resource (one Redpanda configuration property), and scope (cluster, broker, or topic) plus exactly what is returned. It is clearly distinguishable from list_config_properties (enumerates) and ask_redpanda_question (free-form Q&A).

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?

Explicitly says to use this *before* ask_redpanda_question for questions about a specific property's default, type, or availability, and names the platform='cloud' case. The 'exact name' requirement and the alternative behavior for unknown names are both spelled out.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.