Technical debt: Add Logging to Everything

Open
#47 0 comments 0 reactions 1 assignee View on GitHub

@hackingerror404 is already working on this.

Since Mar 23, 2026.

Assessment

This issue has not been assessed yet.

Description

As a developer,
I want to view logs of the exact MCP tool calls made during an LLM interaction,
so that I can verify correctness, trace behavior, and debug issues.

Acceptance Criteria:

  • Logs show:
    - User input
    - Selected MCP tools
    - Tool parameters
    - Raw MCP JSON response
  • Logs are readable during the demo
  • Logging does not alter LLM behavior

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.