Retrieve the current value and metadata of any Houdini parameter by specifying its node path and parameter name.
Get the value and metadata of a parameter.
Args: node_path: Node path. parm_name: Parameter name.
| Name | Required | Description | Default |
|---|---|---|---|
| node_path | Yes | ||
| parm_name | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It implies a read-only lookup through the word 'Get', but it never explicitly states that it does not modify the scene, nor does it describe what happens for missing nodes/parameters or what 'metadata' includes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the core purpose, with a compact argument list. It is efficient, though the Args section is minimally informative rather than genuinely helpful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple getter with two parameters, the description is minimally viable: an agent can infer the call shape. However, the lack of an output schema and the absence of return-format details, node-path syntax, or error behavior leave notable gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, so the description must compensate. However, 'Node path.' and 'Parameter name.' only restate the property titles from the schema and add no meaningful detail about expected formats, examples, or allowed values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it retrieves both the value and metadata of a named parameter. This is clear, but it does not explicitly differentiate it from siblings like get_parameters or get_parameter_schema, so it misses the top score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 get_parameters, get_parameter_schema, or set_parameter. The description only lists arguments and does not mention scenarios, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.