Skip to content

Fix the MCP response of get-profiles-for-document-bundle - #586

Merged
qligier merged 2 commits into
mainfrom
ql-fix-mcp-response
Sep 18, 2026
Merged

qligier merged 2 commits into
mainfrom
ql-fix-mcp-response

Conversation

@qligier

@qligier qligier commented Sep 17, 2026

Copy link
Copy Markdown
Member

No description provided.

@qligier qligier self-assigned this Sep 17, 2026
@qligier
qligier requested review from oliveregger and a lite review from Copilot September 17, 2026 17:58

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The repository requires every PR to include an entry in docs/changelog.md, but no changelog update is included.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This PR fixes the MCP tool response for get-profiles-for-document-bundle in Matchbox Server by returning the correct element type for the payload produced from the document Bundle profile analysis.

Changes:

  • Return BundleResourceProvider.ValidationProfile[] instead of String[] when serializing the MCP payload for document Bundle profile matching.
File summaries
File Description
matchbox-server/src/main/java/ca/uhn/fhir/rest/server/McpMatchboxBridge.java Fixes the MCP payload type returned by get-profiles-for-document-bundle to match the ValidationProfile objects produced by bundle analysis.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@qligier
qligier merged commit 3e16bc6 into main Sep 18, 2026
9 of 10 checks passed
@qligier
qligier deleted the ql-fix-mcp-response branch September 18, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants