Skip to main content
Glama
Sign In
duddy

duddy

by qu15501267889-sketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

duddy_canvas_state

Reads the current ComfyUI canvas snapshot (node count, link count, optional full graph) so agents can inspect existing nodes and avoid duplicates or overlapping placement before planning changes.

Instructions

读取用户当前画布的快照（节点数、连线数、完整 graph）。规划前先看一眼现有画布，避免重复建节点或位置重叠。

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

Input Schema

NameRequiredDescriptionDefault
include_graphNo是否返回完整 graph JSON（可能很大）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It signals a read-only snapshot and enumerates the returned counts, which is useful, but it does not state permission requirements, whether the graph payload can be large or slow (that caveat lives only in the parameter schema), or how large canvases affect the response.

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, no filler: the first enumerates what is returned and the second states the trigger condition and its purpose. Everything the agent needs is front-loaded.

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, single-parameter read tool with no annotations and no output schema, the description adequately enumerates the return shape (node count, edge count, graph). Minor gaps remain around payload size and read-only guarantees, but nothing essential for correct invocation is missing.

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?

With one parameter at 100% schema coverage, the schema already explains include_graph and its default, so the baseline is 3. The description's mention of the '完整 graph' in the snapshot hints at what the flag controls but does not add syntax, cost, or guidance beyond the schema's own note that the payload may be large.

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 uses a clear verb and resource ('读取用户当前画布的快照') and specifies the returned contents ('节点数、连线数、完整 graph'), so it is distinguishable from siblings such as duddy_search_nodes or duddy_node_info. It does not name any sibling explicitly, but the scope is unambiguous.

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 an explicit precondition for use, tied to planning tools like duddy_precheck_plan and duddy_plan_workflow, and states the rationale ('避免重复建节点或位置重叠'). It lacks an explicit when-not or a named alternative to prefer instead, which keeps it below 5.

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