SuperDev

Overview Schema Source Related Servers Discussions Admin

Append log analysis to debug session

append_log_analysis_to_session

Perform deterministic log analysis and append the diagnostic result to the session record, leaving runtime state and configuration unchanged.

Instructions

Run deterministic log analysis and append the result as a local diagnostic record only; it does not change runtime state or configuration.

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": {
      "session_id": "<session_id>",
      "analysis_type": "<analysis_type>"
    },
    "name": "append_log_analysis_to_session"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No
`from`	No
`limit`	No
`since`	No
`after_ms`	No
`trace_id`	No
`before_ms`	No
`project_id`	No
`request_id`	No
`session_id`	Yes
`project_name`	No
`analysis_type`	Yes
`deployment_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description takes on the burden of disclosure. It explicitly states 'it does not change runtime state or configuration' and 'local diagnostic record only', which are critical safety traits. However, it omits other behavioral details such as error conditions, whether a session must exist, or response format, so not a 5.

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 wasted words. It efficiently conveys the action, determinism, and non-mutating nature without redundancy.

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

Completeness2/5

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

For a tool with 13 parameters, no output schema, and no annotations, the description is too sparse. It covers purpose and safety but leaves out operational context needed for correct invocation, such as parameter semantics, expected output, or when to choose this over similar tools. This makes it insufficient for an agent to fully exploit the tool.

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%, and the description provides no parameter-specific meaning. It mentions 'log analysis' but does not explain what analysis_type values (trace, error_window) mean or what the 13 parameters (session_id, from, to, limit, etc.) represent. The parameter names are partially self-explanatory, but the description fails to compensate for the schema gap.

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: 'Run deterministic log analysis and append the result as a local diagnostic record only.' It specifies both the verb and resource, and distinguishes from siblings by noting it is non-mutating and local-only, setting it apart from other analysis tools like analyze_trace_logs or append_debug_session_note.

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 implies usage: run deterministic log analysis and append the result to a debug session, with the caveat of being non-mutating. It provides clear context but does not explicitly mention alternatives or when not to use this tool, so it stops 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.

Deploy Server