log-probe-mcp

Overview Schema Source Related Servers Discussions Admin

Export a debugging session as a written knowledge-base entry

knowledge_base_export

Preserve debugging outcomes by writing a session summary with root cause, hypotheses, and evidence, then updating the knowledge index for future reference.

Instructions

Writes .log-probe/knowledge/.md summarizing the root cause, confirmed/refuted hypotheses with evidence, and notable executions for a session, and refreshes .log-probe/knowledge/INDEX.md linking every exported session. This is the durable, written record analogous to a hand-maintained debugging notes file — call it once a session has reached a conclusion (or is being abandoned) so the investigation isn't lost.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "knowledge_base_export"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the file write and index refresh behavior, and describes the content of the summary. It doesn't mention error conditions or prerequisites, but it adequately conveys the side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted words. The first sentence is front-loaded with the action and resource, and the second adds valuable usage guidance and analogy. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple schema (1 parameter) and no output schema, the description is complete. It explains what files are written, what content is included, when to call, and why it matters, covering all necessary context for an agent to decide.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is 0%, and the description compensates by embedding <sessionId> in the output path, implying the parameter is the session identifier. For a single string parameter with a minLength constraint, this provides sufficient meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool writes a specific file (.log-probe/knowledge/<sessionId>.md) and refreshes an index, using specific verbs and resource names. It distinguishes itself from sibling tools by framing it as the durable, written record, unlike session getters or execution tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly advises calling the tool 'once a session has reached a conclusion (or is being abandoned)', providing clear timing. It doesn't name alternatives or state when not to use it, but the context makes the choice clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.