Log Multi-Step MCP Tool Execution
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
Research direction
Start by locating the MCP tool-call handling used during multi-step conversations and the demo entry point. Determine where a project logger should be created and how calls, parameters, and results currently flow. Done means ordered logs are visible during the demo without using console.error or disrupting conversation flow.
Written by the indexing model from the issue text.
Description
As a developer,
I want to see logs of all MCP tool calls made during a multi-step conversation,
so that I can verify sequencing, state usage, and correctness.
Acceptance Criteria:
- Logs show each tool call in order
- Parameters and results are recorded
- Logs are visible during the demo
- Logging does not interfere with conversation flow
It's important to note that you shouldn't use console.error for logging as this will cause errors in our tests. Most likely this will require us creating and using our own logger. This task may need to be broken up into two parts. Create the logger and then implement the logger.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from Picolab/MCPforEXP
-
Seperate the Enviornments Prod and LocalMay be free again @mmad4804 claimed this 219 days ago, and no pull request is open. Open
-
Refine tool definitionsMay be free again @chancecarr claimed this 233 days ago, and no pull request is open. Open
-
Practice Demo Live and Submit VideoMay be free again @charliethebrown12 claimed this 233 days ago, and no pull request is open. Open
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Get All Tests To Run in DockerMay be free again @braydonlowe claimed this 236 days ago, and no pull request is open. Open
All issues in Picolab/MCPforEXP
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anthropics/claude-plugins-community#3125 ·
Maintainers usually reply within 4 days
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
design enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Imageomics/catalog#158 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day