log-probe-mcp

Overview Schema Source Related Servers Discussions Admin

Get debugging session detail

debug_session_get

Fetch full details of a debugging session, including hypotheses and execution summaries. Output in markdown for easy reading.

Instructions

Fetches full detail for a session: its hypotheses and execution summaries. Use format=markdown for a human-readable rendering.

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": "debug_session_get"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No		json
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description must carry the transparency burden. It discloses the tool's read-only nature ('Fetches'), the content of the response (hypotheses and execution summaries), and behavior related to format selection (markdown vs. default). It does not mention authentication or rate limits, but these are less critical for a simple getter.

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 only two sentences long. The first sentence states the primary purpose and key content, the second delivers a useful parameter hint. There is no filler or redundant information.

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

Completeness4/5

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

For a simple 2-parameter getter with no output schema, the description provides a high-level overview of the returned data (hypotheses and execution summaries) and format behavior. It could elaborate on the response structure, but overall it gives sufficient context for correct invocation.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It adds value by explaining the markdown format's purpose ('human-readable rendering'), but sessionId is only implied by the tool name and title, not explicitly described. The compensation is partial, so a 3 is appropriate.

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 uses a specific verb ('Fetches') and resource ('full detail for a session') and explicitly enumerates what is included ('hypotheses and execution summaries'). This clearly distinguishes it from sibling tools like debug_session_list, debug_session_create, and debug_session_resolve.

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?

The description gives practical usage guidance ('Use format=markdown for a human-readable rendering') and clearly implies the tool is for retrieving session detail. However, it does not explicitly contrast with alternatives like debug_session_list, so it falls short of a 5.

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