fix: pass argument properties to mcp tool#687
Merged
Conversation
cd115f2 to
323f630
Compare
323f630 to
a3fb18e
Compare
0be97ab to
034c5f3
Compare
radu-mocanu
approved these changes
May 6, 2026
034c5f3 to
23f935a
Compare
23f935a to
950de1c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AgentMcpTool.argument_propertieswas parsed fromagent.jsonbut never passed to the constructed tool, so MCP tools with Argument / Text Builder / Static input variants ran as if nothing was configured. The LLM filled those args itself.This switches MCP tools to
StructuredToolWithArgumentPropertiesso the existingStaticArgsHandlerinllm_nodepicks them up. In schema and all modes, the sameargumentPropertiesfromagent.jsonare matched onto server-discovered tools by name.Development Package
uipath pack --nolockto get the latest dev build from this PR (requires version range).