Merge pull request #1256 from tisnik/lcore-1356-updated-doc

LCORE-1356: updated doc

Author: tisnik

docs/config.html

@@ -693,26 +693,31 @@ <h2 id="customization">Customization</h2>
           <td/>
         </tr>
         <tr class="odd">
+          <td>disable_shield_ids_override</td>
+          <td>boolean</td>
+          <td/>
+        </tr>
+        <tr class="even">
           <td>system_prompt_path</td>
           <td>string</td>
           <td/>
         </tr>
-        <tr class="even">
+        <tr class="odd">
           <td>system_prompt</td>
           <td>string</td>
           <td/>
         </tr>
-        <tr class="odd">
+        <tr class="even">
           <td>agent_card_path</td>
           <td>string</td>
           <td/>
         </tr>
-        <tr class="even">
+        <tr class="odd">
           <td>agent_card_config</td>
           <td>object</td>
           <td/>
         </tr>
-        <tr class="odd">
+        <tr class="even">
           <td>custom_profile</td>
           <td/>
           <td/>
@@ -1056,13 +1061,26 @@ <h2 id="modelcontextprotocolserver">ModelContextProtocolServer</h2>
           <td>authorization_headers</td>
           <td>object</td>
           <td>Headers to send to the MCP server. The map contains the header name
-and the path to a file containing the header value (secret). There are 2
+and the path to a file containing the header value (secret). There are 3
 special cases: 1. Usage of the kubernetes token in the header. To
 specify this use a string &#x2018;kubernetes&#x2019; instead of the file path. 2.
-Usage of the client provided token in the header. To specify this use a
-string &#x2018;client&#x2019; instead of the file path.</td>
+Usage of the client-provided token in the header. To specify this use a
+string &#x2018;client&#x2019; instead of the file path. 3. Usage of the oauth token in
+the header. To specify this use a string &#x2018;oauth&#x2019; instead of the file
+path.</td>
         </tr>
         <tr class="odd">
+          <td>headers</td>
+          <td>array</td>
+          <td>List of HTTP header names to automatically forward from the incoming
+request to this MCP server. Headers listed here are extracted from the
+original client request and included when calling the MCP server. This
+is useful when infrastructure components (e.g.&#xA0;API gateways) inject
+headers that MCP servers need, such as x-rh-identity in HCC. Header
+matching is case-insensitive. These headers are additive with
+authorization_headers and MCP-HEADERS.</td>
+        </tr>
+        <tr class="even">
           <td>timeout</td>
           <td>integer</td>
           <td>Timeout in seconds for requests to the MCP server. If not specified,

docs/config.json

@@ -583,6 +583,11 @@
             "title": "Disable Query System Prompt",
             "type": "boolean"
           },
+          "disable_shield_ids_override": {
+            "default": false,
+            "title": "Disable Shield Ids Override",
+            "type": "boolean"
+          },
           "system_prompt_path": {
             "type": "string",
             "nullable": true,
@@ -866,10 +871,18 @@
             "additionalProperties": {
               "type": "string"
             },
-            "description": "Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 2 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client provided token in the header. To specify this use a string 'client' instead of the file path.",
+            "description": "Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header. To specify this use a string 'client' instead of the file path. 3. Usage of the oauth token in the header. To specify this use a string 'oauth' instead of the file path. ",
             "title": "Authorization headers",
             "type": "object"
           },
+          "headers": {
+            "description": "List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS.",
+            "items": {
+              "type": "string"
+            },
+            "title": "Propagated headers",
+            "type": "array"
+          },
           "timeout": {
             "type": "integer",
             "nullable": true,

docs/config.md

@@ -209,6 +209,7 @@ Service customization.
 |-------|------|-------------|
 | profile_path | string |  |
 | disable_query_system_prompt | boolean |  |
+| disable_shield_ids_override | boolean |  |
 | system_prompt_path | string |  |
 | system_prompt | string |  |
 | agent_card_path | string |  |
@@ -372,7 +373,7 @@ Useful resources:
 | name | string | MCP server name that must be unique |
 | provider_id | string | MCP provider identification |
 | url | string | URL of the MCP server |
-| authorization_headers | object | Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header — use the string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header — use the string 'client' instead of the file path. 3. Usage of OAuth token (resolved at request time or 401 with WWW-Authenticate) — use the string 'oauth' instead of the file path. |
+| authorization_headers | object | Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header. To specify this use a string 'client' instead of the file path. 3. Usage of the oauth token in the header. To specify this use a string 'oauth' instead of the file path.  |
 | headers | array | List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS. |
 | timeout | integer | Timeout in seconds for requests to the MCP server. If not specified, the default timeout from Llama Stack will be used. Note: This field is reserved for future use when Llama Stack adds timeout support. |
 

docs/openapi.json

@@ -4447,7 +4447,7 @@
                 ],
                 "summary": "Handle A2A Jsonrpc",
                 "description": "Handle A2A JSON-RPC requests following the A2A protocol specification.\n\nThis endpoint uses the DefaultRequestHandler from the A2A SDK to handle\nall JSON-RPC requests including message/send, message/stream, etc.\n\nThe A2A SDK application is created per-request to include authentication\ncontext while still leveraging FastAPI's authorization middleware.\n\nAutomatically detects streaming requests (message/stream JSON-RPC method)\nand returns a StreamingResponse to enable real-time chunk delivery.\n\nArgs:\n    request: FastAPI request object\n    auth: Authentication tuple\n    mcp_headers: MCP headers for context propagation\n\nReturns:\n    JSON-RPC response or streaming response",
-                "operationId": "handle_a2a_jsonrpc_a2a_post",
+                "operationId": "handle_a2a_jsonrpc_a2a_get",
                 "responses": {
                     "200": {
                         "description": "Successful Response",
@@ -4465,7 +4465,7 @@
                 ],
                 "summary": "Handle A2A Jsonrpc",
                 "description": "Handle A2A JSON-RPC requests following the A2A protocol specification.\n\nThis endpoint uses the DefaultRequestHandler from the A2A SDK to handle\nall JSON-RPC requests including message/send, message/stream, etc.\n\nThe A2A SDK application is created per-request to include authentication\ncontext while still leveraging FastAPI's authorization middleware.\n\nAutomatically detects streaming requests (message/stream JSON-RPC method)\nand returns a StreamingResponse to enable real-time chunk delivery.\n\nArgs:\n    request: FastAPI request object\n    auth: Authentication tuple\n    mcp_headers: MCP headers for context propagation\n\nReturns:\n    JSON-RPC response or streaming response",
-                "operationId": "handle_a2a_jsonrpc_a2a_post",
+                "operationId": "handle_a2a_jsonrpc_a2a_get",
                 "responses": {
                     "200": {
                         "description": "Successful Response",
@@ -8843,6 +8843,7 @@
                 "properties": {
                     "contents": {
                         "type": "string",
+                        "maxLength": 65536,
                         "title": "Contents",
                         "description": "File contents read on client",
                         "default": "",
@@ -8898,6 +8899,7 @@
                 "properties": {
                     "stdin": {
                         "type": "string",
+                        "maxLength": 65536,
                         "title": "Stdin",
                         "description": "Redirect input from stdin",
                         "default": "",
@@ -8965,6 +8967,7 @@
                 "properties": {
                     "question": {
                         "type": "string",
+                        "maxLength": 10240,
                         "minLength": 1,
                         "title": "Question",
                         "description": "User question",
@@ -9073,6 +9076,7 @@
                 "properties": {
                     "output": {
                         "type": "string",
+                        "maxLength": 65536,
                         "title": "Output",
                         "description": "Terminal output from client",
                         "default": "",