Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_cop_info

Fetches information about a COP node using its node path, enabling you to inspect node properties and settings in Houdini.

Instructions

Get information about a COP node.

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": {
      "node_path": "<node_path>"
    },
    "name": "get_cop_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does not state that the operation is read-only, what kind of information is returned, what happens when the node does not exist, or whether cooking/evaluation occurs as a side effect.

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

Conciseness3/5

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

One short sentence with no filler, which is efficient. However, the brevity is a product of under-specification rather than disciplined editing, so it earns only a middling score.

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?

With no annotations, no output schema and zero parameter documentation, the definition leaves an agent without the information needed to call it correctly or interpret results. For a lookup tool in a crowded info-tool family, it should at least describe the path argument and the returned content.

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 single parameter node_path is documented nowhere but its name. The description does not explain the expected path syntax (e.g. absolute vs relative node path) or whether it must reference an existing COP node, leaving the required argument ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Get") and a resource ("information about a COP node"), so the general intent is clear. But "information" is vague and it does nothing to distinguish this tool from close siblings such as get_node_info, get_cop_geometry, get_cop_layer or get_cop_vdb, which an agent would have to disambiguate by name alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many sibling info tools, no prerequisites, and no exclusions. The agent must infer that this is the generic COP-node lookup and that the more specific get_cop_* tools cover narrower aspects.

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