Repository navigation
Support for metadata propagation in MCP tool calls #1255
Replies: 1 comment
|
The feature is still wanted and PR #602 has now been updated for the current v2 API. The current design adds an optional provider with this shape: type MetadataProvider func(ctx agent.Context) (map[string]any, error)Its result is assigned to It is not released yet. The implementation has approval and the code checks are green, but the PR's Google CLA check is still tied to the original PR author. The maintainer said it is ready to merge once that clears; if the author does not want to sign, they can land a separate credited PR instead: maintainer follow-up. So the practical status is: implementation ready, administrative merge blocker remaining, and no release number/date promised yet. I would track #602 for the merge and subsequent release notes. If you must test it before release, pinning a test build to the PR commit is possible, but I would not treat that API as stable until it lands on |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
In my use case, I would like to propagate tracing context to MCP server tool call through _meta.
I see PR (#602) addressing this problem.
Any plan to add this support in SDK for coming release(s)?
All reactions