Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_sticky_notes

Deletes sticky notes under a specified Houdini network, including nested networks, to clear annotations in one action.

Instructions

Delete sticky notes under a network, including nested networks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parent_path": "<parent_path>"
    },
    "name": "delete_sticky_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
recursiveNo
parent_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the operation deletes sticky notes and affects nested networks, but it does not explain irreversibility, permission requirements, what happens when no notes exist, or how the recursive parameter changes the effect.

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?

The description is a single front-loaded sentence with no wasted wording. It is efficient, though its brevity contributes to ambiguity around the recursive parameter.

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

Completeness2/5

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

This is a destructive mutation tool with no annotations, no output schema, and 0% parameter description coverage. The one-sentence description is not complete enough to safely guide invocation, because it omits recursive behavior, path format, and reversibility.

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

Parameters2/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 compensate for both parameters. It only vaguely gestures at parent_path as the network location and at recursion via 'including nested networks,' but it gives no path format and does not explain what recursive=false does.

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 gives a specific verb and resource: delete sticky notes, scoped to a network and nested networks. This distinguishes it from create_sticky_note, though it does not explicitly name or compare against alternatives.

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 implied by the scope 'under a network, including nested networks,' which tells the agent the general situation for this tool. It does not state when not to use it, prerequisites, or alternatives for broader deletion tasks.

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