Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_prims

Read primitive data and attributes from a Houdini node with pagination controls, using start, count, group, and attribute filters.

Instructions

Read primitive data and attributes with pagination.

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

Input Schema

NameRequiredDescriptionDefault
countNo
groupNo
startNo
node_pathYes
attributesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 burden. It does disclose one behavioral trait beyond the schema — pagination — but says nothing about default page size behavior in practice, ordering, whether reads are scoped to a subtree, or failure behavior for invalid node paths.

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?

A single short sentence with no wasted words, but it is under-specified rather than concise — the brevity comes at the cost of routing and parameter meaning.

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?

For a five-parameter tool with no annotations, no output schema, and 0% schema description coverage, one sentence is not enough to let an agent call it correctly; the pagination contract and the group/attributes filters remain undefined.

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?

Schema description coverage is 0%, so the description must compensate, and it only hints at two of the five parameters ("attributes" and pagination via count/start). It adds no meaning for node_path, group, or the semantics of start/count beyond their bare titles and defaults.

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 names a specific verb and resource ("Read primitive data and attributes"), which is clearer than a tautology, but "primitive data" is vague and nothing distinguishes this from siblings like get_attrib_values, list_usd_prims, or find_usd_prims that plausibly return overlapping data.

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 when-to-use guidance at all — no indication of when this tool is preferable to get_attrib_values, list_usd_prims, or get_last_modified_prims, and no stated prerequisites beyond the implicit node_path requirement.

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