Skip to main content
Glama
JTCHE

HoudiniMCP

by JTCHE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pdg

Destructive

Cook a TOP network, and read what its work items did.

Instructions

Cook a TOP network, and read what its work items did.

Modes: status, workitems, cook, dirty, cancel.

Use it for a TOP network only. A TOP node does not cook like a SOP: it
makes work items, and each item runs on its own. For a SOP or a DOP, use
cook. For a ROP, use render.

mode:
    "status"    — the counts for each state, and whether a cook runs now.
    "workitems" — the items. `state` filters, for example "failed".
    "cook"      — start the cook. The call comes back at once; read
                  "status" after it to follow the work.
    "dirty"     — mark the node dirty. `dirty_all` also removes the
                  outputs on disk.
    "cancel"    — stop the cook that runs now.

Returns JSON. A failed item holds the command and the log path: read those
before you change the network.

Input Schema

NameRequiredDescriptionDefault
modeNoOne of "status", "workitems", "cook", "dirty", "cancel".status
pathYesThe TOP network or the TOP node.
stateNoworkitems: keep the items in this state, for example "failed" or "cooked".
dirty_allNodirty: also remove the outputs of the node on disk.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.7.3
    • removedInput schema / properties / dirty_all / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / dirty_all / description
      Added value: +"dirty: also remove the outputs of the node on disk."
    • removedInput schema / properties / dirty_all / title
      Removed value: -"Dirty All"
    • addedInput schema / properties / dirty_all / type
      Added value: +"boolean"
    • removedInput schema / properties / mode / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / mode / description
      Added value: +"One of \"status\", \"workitems\", \"cook\", \"dirty\", \"cancel\"."
    • removedInput schema / properties / mode / title
      Removed value: -"Mode"
    • addedInput schema / properties / mode / type
      Added value: +"string"
    • addedInput schema / properties / path / description
      Added value: +"The TOP network or the TOP node."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • removedInput schema / properties / state / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / state / default
      Removed value: -null
    • addedInput schema / properties / state / description
      Added value: +"workitems: keep the items in this state, for example \"failed\" or \"cooked\"."
    • removedInput schema / properties / state / title
      Removed value: -"State"
    • addedInput schema / properties / state / type
      Added value: +"string"
    • removedInput schema / title
      Removed value: -"toolArguments"
  2. Addedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructive=true, but the description adds the context that matters: 'cook' returns at once and must be followed by a status read, 'dirty_all' removes outputs on disk, 'cancel' stops the running cook, and failed items carry the command and log path. This is genuine behavioral detail beyond the annotation flags.

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?

Front-loaded purpose, then modes, then a returns note; the mode list is a scannable structure. Slight redundancy between 'Use it for a TOP network only' and 'A TOP node does not cook like a SOP' costs a point.

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

Completeness5/5

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

With an output schema present, the description needn't document return shape, yet it still flags the actionable payload of a failed item (command and log path) and the async nature of the cook. Nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the semantics of each mode value and how 'state' filters workitems ("failed") and how 'dirty_all' removes on-disk outputs. That is more than the schema's one-line field descriptions, though it largely mirrors them.

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?

States a concrete verb and resource ('Cook a TOP network, and read what its work items did') and immediately scopes it to TOP networks as distinct from SOP/DOP/ROP. An agent can distinguish it from cook and render without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names when to use it ('Use it for a TOP network only') and routes to the alternatives with conditions: 'For a SOP or a DOP, use cook. For a ROP, use render.' The mode list further tells the agent which mode answers which question.

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