[josemontespg]

Summary

This PR adds catalogs/mcp/v1/examples/mcp-json-tool-result.json, a message sequence that loads the open issues of a repository from a headless list_issues tool, next to the basic catalog. One button chains callMcpTool, transformData and updateDataModel to fill a template list from the json of the payload; a second button only sets targetDataPath and binds a list to the structuredContent of the payload written there.

catalog.test.ts processes the example with a mock client that returns the issues both as JSON text and as structured content, runs both button actions through DataContext.resolveAction, and checks the data model after each. Both READMEs now point at the example from the sections that use its actions.

Changes

• catalogs/mcp/v1/examples/mcp-json-tool-result.json: the example surface, with load_button (chained functions into /issues) and load_all_button (targetDataPath: "/issueResponse").
• typescript/catalogs/mcp/src/catalog.test.ts: createToolClient and actionOf helpers and three cases: the example processes next to the basic catalog, the first action writes the shaped issues to /issues, the second writes the payload to /issueResponse.
• catalogs/mcp/README.md: list the example and reference its two buttons from the data functions section.
• typescript/catalogs/mcp/README.md: link the example from "Shape a headless tool result".

Verification

• yarn workspace @a2ui/catalog-mcp run test: node and karma suites pass, including the three new the JSON tool result example cases.
• specification/v1_0/test/run_tests.py validates the example against the v1 MCP and basic catalogs; ./scripts/fix_format.sh --check passes.

[gemini-code-assist]

Code Review

This pull request introduces a new example file mcp-json-tool-result.json that demonstrates two ways to load and handle headless MCP tool results: by chaining data functions (callMcpTool, transformData, and updateDataModel) or by utilizing targetDataPath. The documentation in both the main and TypeScript catalog READMEs has been updated to reference this example, and corresponding unit tests have been added to catalog.test.ts. Feedback on the changes suggests improving the robustness of the mock MCP client in the tests by using optional chaining to safely handle potentially undefined request parameters.