feat: add tool_type metadata to all tools #401
Conversation
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
Add tool_type and display_name metadata to integration tools for better identification and display purposes. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
saksharthakkar
changed the title
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
saksharthakkar
force-pushed
the
feat/integration-tool-metadata
branch
from
a2fa79d to
319224a
Compare
Add tool_type and display_name metadata to context tools (semantic search, deep rag, batch transform) and mcp tools for completeness. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
saksharthakkar
changed the title
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Add
tool_typeanddisplay_namemetadata to all tool types for completeness:Note: Process and escalation tools already have this metadata.
Why
This metadata is consumed by
uipath-agents-pythonto create custom OTEL spans per tool type. See PR #87 which usestool_typeto identify integration tools and create proper child spans withIntegrationToolSpanAttributes.Without this metadata, the callback code in uipath-agents-python cannot distinguish tool types for observability.
Test plan
tool_typeanddisplay_namemetadata🤖 Generated with Claude Code