fix(mcp-kafka-connect,mcp-schema-registry): correct structuredContent claims for tools without an outputSchema

structuredContent always carries the raw upstream JSON response, whether
or not schemas.output is declared -- the schema only adds validation and
pruning. The initial pass incorrectly said several tools returned
"content text summary only", implying structuredContent was withheld;
it isn't.

Author: claude

src/reference/config/bindings/mcp-kafka-connect/.partials/tools.md

@@ -1,4 +1,4 @@
-The `mcp-kafka-connect` client exposes a fixed set of intrinsic tools, derived from a bundled Kafka Connect REST API specification — there is no `options.tools` to author, and no upstream server or spec to select. Each tool's `inputSchema` validates `tools/call` `arguments` before Zilla dispatches the matching request to `options.server`; a tool with no fixed `outputSchema` still returns a result, either as `structuredContent` mirroring the raw upstream JSON response or as `content` text only.
+The `mcp-kafka-connect` client exposes a fixed set of intrinsic tools, derived from a bundled Kafka Connect REST API specification — there is no `options.tools` to author, and no upstream server or spec to select. Each tool's `inputSchema` validates `tools/call` `arguments` before Zilla dispatches the matching request to `options.server`. Every tool's `structuredContent` carries the upstream JSON response — validated and pruned to a declared `outputSchema` where one exists, or the raw body unchanged where none is declared — and `content` carries the tool's `summary` text, which may itself interpolate fields out of that same response via `${result.x}`.
 
 ### list_connectors
 
@@ -8,7 +8,7 @@ Lists the names of every connector on the worker.
 
 No arguments.
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response — an array of connector names — with no fixed property list.
 
 ### create_connector
 
@@ -21,7 +21,7 @@ Creates a new connector.
 | `name` | `string` | Yes | Connector name. |
 | `config` | `object` as map of named `string` | Yes | Connector configuration properties. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### describe_connector
 
@@ -33,7 +33,7 @@ Reads one connector's configuration and task list by name.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to describe. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### delete_connector
 
@@ -45,7 +45,7 @@ Deletes a connector.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to delete. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### describe_connector_config
 
@@ -71,7 +71,7 @@ Creates or updates a connector by setting its full configuration.
 | `connector.class` | `string` | Yes | Connector class to instantiate. |
 | `tasks.max` | `string` | Yes | Maximum number of tasks to run. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### validate_connector_config
 
@@ -85,7 +85,7 @@ Validates a connector configuration against a plugin's configuration definition,
 | `connector.class` | `string` | Yes | Connector class to validate. |
 | `tasks.max` | `string` | Yes | Maximum number of tasks to validate. |
 
-No `outputSchema` is declared; the result is a `content` text summary only, such as `Validated connector config with 0 errors`.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.error_count}`, such as `Validated connector config with 0 errors`.
 
 ### describe_connector_status
 
@@ -97,7 +97,7 @@ Reads a connector's current state and the state of each of its tasks.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to check the status of. |
 
-No `outputSchema` is declared; the result is a `content` text summary only, such as `Connector my-connector is RUNNING`.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}` and `${result.connector.state}`, such as `Connector my-connector is RUNNING`.
 
 ### restart_connector
 
@@ -109,7 +109,7 @@ Restarts a connector.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to restart. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### pause_connector
 
@@ -121,7 +121,7 @@ Pauses a connector and all of its tasks.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to pause. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### resume_connector
 
@@ -133,7 +133,7 @@ Resumes a paused connector and all of its tasks.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to resume. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### stop_connector
 
@@ -145,7 +145,7 @@ Stops a connector and shuts down all of its tasks, without deleting the connecto
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector to stop. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.name}`.
 
 ### list_connector_tasks
 
@@ -157,7 +157,7 @@ Lists every task belonging to a connector.
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector whose tasks to list. |
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list.
 
 ### restart_connector_task
 
@@ -197,7 +197,7 @@ Overwrites a connector's source or sink offsets. The connector must be stopped f
 | `offsets[].partition` | `object` | Yes | Source partition or sink topic-partition identifying the offset. |
 | `offsets[].offset` | `object` | Yes | New offset value for the identified partition. |
 
-No `outputSchema` is declared; the result is a `content` text summary only, interpolated from the upstream response, such as `${result.message}`.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.message}`.
 
 ### reset_connector_offsets
 
@@ -209,7 +209,7 @@ Resets a connector's source or sink offsets to their initial state. The connecto
 | --- | --- | --- | --- |
 | `connector` | `string` | Yes | Connector whose offsets to reset. |
 
-No `outputSchema` is declared; the result is a `content` text summary only, interpolated from the upstream response, such as `${result.message}`.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response, with no fixed property list. The summary interpolates `${result.message}`.
 
 ### list_connector_plugins
 
@@ -219,4 +219,4 @@ Lists every connector plugin installed on the worker.
 
 No arguments.
 
-No `outputSchema` is declared; the result is a `content` text summary only.
+No fixed `outputSchema` is declared; the result's `structuredContent` mirrors the raw upstream JSON response — an array of installed plugins — with no fixed property list.

src/reference/config/bindings/mcp-schema-registry/.partials/tools.md

@@ -1,11 +1,13 @@
-The `mcp-schema-registry` client exposes a fixed set of intrinsic tools, derived from a bundled schema registry API specification — there is no `options.tools` to author, and no upstream server or spec to select. Each tool's `inputSchema` validates `tools/call` `arguments` before Zilla dispatches the matching request to `options.server`. None of these tools declare a fixed `outputSchema`; each returns a `content` text summary, though the summary may interpolate fields of the raw upstream JSON response, such as `${result.id}`.
+The `mcp-schema-registry` client exposes a fixed set of intrinsic tools, derived from a bundled schema registry API specification — there is no `options.tools` to author, and no upstream server or spec to select. Each tool's `inputSchema` validates `tools/call` `arguments` before Zilla dispatches the matching request to `options.server`. None of these tools declare a fixed `outputSchema`, so each tool's `structuredContent` mirrors the raw upstream JSON response with no fixed property list, and its `summary` text may interpolate fields out of that same response, such as `${result.id}`.
 
 ### list_subjects
 
 Lists every subject registered in the schema registry.
 
 No arguments.
 
+The result's `structuredContent` mirrors the raw upstream JSON response — an array of subject names.
+
 ### describe_subject
 
 Lists the schema version numbers registered for a subject.
@@ -14,6 +16,8 @@ Lists the schema version numbers registered for a subject.
 | --- | --- | --- | --- |
 | `subject` | `string` | Yes | Subject to list versions for. |
 
+The result's `structuredContent` mirrors the raw upstream JSON response — an array of version numbers.
+
 ### register_schema
 
 Registers a new schema version under a subject.
@@ -24,6 +28,8 @@ Registers a new schema version under a subject.
 | `schema` | `string` | Yes | Schema document to register. |
 | `schemaType` | `string` | No | Schema format, such as `AVRO`, `JSON`, or `PROTOBUF`. Defaults to `AVRO` when omitted. |
 
+The summary interpolates `${result.id}`, such as `Registered schema with id 1`.
+
 ### get_schema
 
 Retrieves a specific registered schema version for a subject.
@@ -33,6 +39,8 @@ Retrieves a specific registered schema version for a subject.
 | `subject` | `string` | Yes | Subject to read from. |
 | `version` | `string` | Yes | Schema version number, or `latest`. |
 
+The summary interpolates `${result.id}` and `${result.version}`, such as `Retrieved schema id 1, version 1`.
+
 ### delete_schema_version
 
 Deletes a specific registered schema version for a subject.
@@ -50,6 +58,8 @@ Deletes a subject and every schema version registered under it.
 | --- | --- | --- | --- |
 | `subject` | `string` | Yes | Subject to delete. |
 
+The result's `structuredContent` mirrors the raw upstream JSON response — an array of the deleted subject's version numbers.
+
 ### check_compatibility
 
 Checks whether a schema is compatible with a specific already-registered version of a subject.
@@ -61,6 +71,8 @@ Checks whether a schema is compatible with a specific already-registered version
 | `schema` | `string` | Yes | Schema document to check. |
 | `schemaType` | `string` | No | Schema format, such as `AVRO`, `JSON`, or `PROTOBUF`. Defaults to `AVRO` when omitted. |
 
+The summary interpolates `${result.is_compatible}`, such as `Compatibility check result: true`.
+
 ### get_compatibility
 
 Reads the compatibility level configured for a subject.
@@ -69,6 +81,8 @@ Reads the compatibility level configured for a subject.
 | --- | --- | --- | --- |
 | `subject` | `string` | Yes | Subject to read the compatibility level of. |
 
+The summary interpolates `${result.compatibilityLevel}`, such as `Compatibility level is FULL`.
+
 ### set_compatibility
 
 Sets the compatibility level for a subject.
@@ -77,3 +91,5 @@ Sets the compatibility level for a subject.
 | --- | --- | --- | --- |
 | `subject` | `string` | Yes | Subject to set the compatibility level of. |
 | `compatibility` | `string` | Yes | Compatibility level, such as `BACKWARD`, `FORWARD`, `FULL`, or `NONE`. |
+
+The summary interpolates `${result.compatibility}`, such as `Compatibility level set to FULL`.