Log Multi-Step MCP Tool Execution

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Picolab/MCPforEXP

All issues in Picolab/MCPforEXP

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.