Skip to main content
Glama
Sign In
duddy

duddy

by qu15501267889-sketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

duddy_ping

Checks whether the duddy extension is online, helping you distinguish a stopped ComfyUI instance from a missing extension before starting canvas work.

Instructions

检查 duddy 扩展是否在线。第一次接触 ComfyUI 时先调这个，能立刻区分「ComfyUI 没开」和「扩展没装」两种故障。

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_ping"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full behavioral burden. It discloses the diagnostic behavior and the two failure modes it separates, which implies a safe read-only check, but it does not state the return shape, side-effect guarantees, or latency.

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 compact sentences, front-loaded with the core action and then the first-use rule. Every sentence contributes useful routing or diagnostic context with no wasted wording.

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?

For a zero-parameter health check, the description supplies the key context: when to call it and which failures it disambiguates. However, because there is no output schema and no annotations, it does not define what a successful or offline result looks like, leaving return semantics to inference.

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

Parameters4/5

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

The tool has zero parameters and schema description coverage is 100%, so there is no parameter meaning for the description to add. The baseline for a parameterless tool is 4.

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 and resource: it checks whether the duddy extension is online. It identifies the tool as a connectivity/health check rather than an event, planning, canvas, or log operation, so it is easy to distinguish from the sibling tools.

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?

It gives explicit timing guidance: call this first when first interacting with ComfyUI. It also explains the intended diagnostic use, distinguishing 'ComfyUI not running' from 'extension not installed'. It does not name explicit alternatives or when-not-to-use conditions.

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

Deploy Server

Other Tools