duddy

duddy_get_logs

Reads ComfyUI runtime logs, including node prints, to troubleshoot generation errors, loading failures, or stalled jobs. Filter by level, line limit, or keyword to find causes fast.

Instructions

读 ComfyUI 的运行日志（包含节点里的 print）。出图报错、加载失败、卡住不动时，先看日志再猜原因。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "duddy_get_logs"
  }
}

Input Schema

Name	Required	Description
`level`	No	ERROR / WARNING / PRINT 等，可空
`limit`	No
`contains`	No	只返回包含该子串的行

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden. It usefully discloses that node-level print output is included, but says nothing about whether access is read-only (only implied by '读'), whether output is tail-truncated, how entries are ordered, or whether logs survive restarts.

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?

Two short sentences, zero filler: the first states what is returned, the second states when to reach for it. Front-loaded and easy to scan.

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 simple (3 optional params, no output schema), and the description covers what comes back and why to call it. It still leaves key call-shaping behavior — how limit bounds the response and in what order lines arrive — unaddressed for an agent deciding how to invoke it.

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 coverage is 67%: level and contains are documented in the schema, but limit has only a default of 80 with no explanation. The description mentions no parameters at all, so it adds nothing about what limit counts (lines vs. entries) or how filtering interacts with it.

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

Purpose4/5

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

States a specific verb and resource ('读 ComfyUI 的运行日志') and narrows scope with a useful detail ('包含节点里的 print'). This distinguishes it from a generic event feed like duddy_events, though the description never names that sibling explicitly.

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?

Gives concrete triggering situations ('出图报错、加载失败、卡住不动') and an explicit ordering rule ('先看日志再猜原因'), which tells the agent to consult this before hypothesizing. It stops short of naming alternatives such as duddy_run_status or duddy_events for related states.

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

Deploy Server