Skip to main content
Glama

get_logs

Read-only

Retrieve recent ComfyUI log lines to troubleshoot issues, optionally filtering by text to isolate errors or specific events.

Instructions

The last lines of the ComfyUI log (max 500). contains= keeps only lines with that text, e.g. "error".

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

Input Schema

NameRequiredDescriptionDefault
linesNo
containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond that: the 500-line hard cap, meaning output can be truncated. It says nothing about tail semantics when the log is empty, missing, or being rotated.

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

Conciseness4/5

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

Two short sentences, front-loaded with the resource and scope, with zero padding. The telegraphic "contains= keeps only lines with that text" phrasing is compact but slightly informal for a spec.

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 two-parameter read tool with full annotation coverage and no output schema, the description covers purpose, the truncation cap, and the one non-obvious filter parameter. Only edge-case behavior (log absent, filtering with no matches) is left unstated, which is a minor gap.

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 carry parameter meaning. It explains `contains` well with a concrete example, but never explicitly says that `lines` controls how many trailing lines are returned - that is only inferable from "last lines (max 500)" and the schema default of 80.

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?

The description names the specific resource (ComfyUI log) and what portion is returned (the last lines, capped at 500), so an agent knows exactly what it gets back. It does not differentiate against adjacent status/diagnostic siblings, but the verb+resource statement is clear.

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?

Usage is only implied: the "error" example hints that this is for scanning recent log output for problems. There is no explicit statement of when to prefer this over comfyui_status or diagnose_job, and no exclusions.

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