log-probe-mcp

by asynchroza

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List executions in a session

execution_list

List executions in a debugging session with log-count summaries, ordered by most recent.

Instructions

Lists executions for a debugging session with log-count summaries, most recent first.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It does reveal that results include log-count summaries and are ordered most recent first, which is helpful. However, it omits pagination behavior, default limits, authentication requirements, and error semantics, leaving gaps for a list operation with a limit parameter.

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 a single, front-loaded sentence with zero redundancy. Every phrase adds value: action, scope, summary detail, and ordering.

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

Completeness3/5

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

The tool is relatively simple (2 params, no output schema), but the description does not fully compensate for the missing output schema. It mentions log-count summaries but not the actual fields returned, and it omits how `limit` affects the result set or pagination.

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

Parameters2/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 for both parameters. It implicitly covers sessionId via 'for a debugging session,' but the `limit` parameter is completely undocumented—no mention of limiting the number of results or its maximum value of 200.

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 action ('Lists executions') and scopes it to a debugging session, with useful detail ('log-count summaries, most recent first'). This distinguishes it from sibling tools like execution_get_logs (which retrieves logs for a single execution) and execution_create/run/end (which are mutations).

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

Usage Guidelines3/5

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

The description implies usage for enumerating executions in a session but does not explicitly state when to use this tool over alternatives. Sibling tools like execution_get_logs and execution_compare exist, but no guidance on choosing between them is provided.

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