Search needed in Traces
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 10
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 17
Description
With traces, one can check all the MCP tool calls that have happened. However, during the workflow execution, hundreds of such MCP tool calls might happen. Currently, all of those calls are captured in the traces, but if I have to search for specific tool call, then it is not possible.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the traces entry point and how MCP tool calls are represented within a workflow execution. Determine how a user should search the captured calls, including the matching scope and expected results, then verify the behavior with a workflow containing many tool calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100