Skip to main content
Glama

get_parameters

Read many parameter values at once, matched by name or label substring.

Instructions

Read many parameter values at once, matched by name or label substring.

The batch counterpart of set_parameters. Several unrelated groups of settings ("flame", "wind", "buoy") come back in one call instead of one call each, and unlike get_node_card these are the live values on this node rather than the defaults for its type.

Pass inside instead of node_path to read the same patterns across a whole network in one call: "every file parm of this material library, unexpanded" comes back as rows of {node, parm, value, raw_value}, up to 2000 rows. raw_value is the unexpanded text ($JOB/...), shown when it differs from the value, exactly as for a single node.

Args: node_path: Node to read. patterns: Substrings matched against parameter name and label. Omit for everything, up to the cap. Required with inside, unless non_default_only or value_contains. include_defaults: Also report whether each value is still the default, and, where it differs, the default (default, default_expression). inside: Network to read instead of a single node. recursive: With inside, include every descendant, not only children. Nodes inside locked HDAs (a solver's own internals) are skipped and counted in skipped_inside_locked_assets. node_type: With inside, only nodes of this type (e.g. "mtlximage"). include_locked_assets: With recursive, read inside locked HDAs too. value_contains: Only parameters whose raw text or expression holds this substring (case-insensitive), e.g. inside="/", recursive=True, value_contains="/obj/X": every parameter that still names that node by its absolute path, a deleted one included. A relative "../X" is not "/obj/X": search "X" to catch those. No patterns needed. non_default_only: Only parameters changed from their defaults, each with its default: "what was changed on every node of this network" in one call (with inside, no patterns needed). A changed ramp is one entry holding all its keys; its key parms (ramp2pos...) are listed only when a pattern names them and not the ramp.

Input Schema

NameRequiredDescriptionDefault
insideNo
patternsNo
node_pathNo
node_typeNo
recursiveNo
value_containsNo
include_defaultsNo
non_default_onlyNo
include_locked_assetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.27.0
    • addedInput schema / properties / value_contains
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Value Contains"
      +}
  2. Changed1 schema field changedv2.25.0
    • addedInput schema / properties / non_default_only
      Added value: +{
      +  "default": false,
      +  "title": "Non Default Only",
      +  "type": "boolean"
      +}
  3. Changed2 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / include_locked_assets
      Added value: +{
      +  "default": false,
      +  "title": "Include Locked Assets",
      +  "type": "boolean"
      +}
  4. Changed7 schema fields changedv2.21.0
    • addedInput schema / properties / inside
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Inside"
      +}
    • addedInput schema / properties / node_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / node_path / default
      Added value: +null
    • removedInput schema / properties / node_path / type
      Removed value: -"string"
    • addedInput schema / properties / node_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Node Type"
      +}
    • addedInput schema / properties / recursive
      Added value: +{
      +  "default": false,
      +  "title": "Recursive",
      +  "type": "boolean"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "node_path"
      -]
  5. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations the description carries the full burden and delivers: a 2000-row cap, locked-HDA skipping counted in `skipped_inside_locked_assets`, raw_value shown only when it differs, and ramp edge cases (a changed ramp is one entry; key parms listed only when named). Return shape {node, parm, value, raw_value} is disclosed.

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 with the core purpose, then structured around a scannable Args block. It is long and the worked examples are dense, but given 9 undocumented parameters almost every sentence earns its place; slightly verbose in places.

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?

A complex 9-parameter tool with no annotations and no output schema, yet the description explains the return rows, the cap, and the locked-asset/ramp exceptions. Nothing an agent needs 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.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it documents all 9 parameters: node_path, patterns (omit-for-everything and required-with-inside conditionality), include_defaults, inside, recursive, node_type, include_locked_assets, value_contains, and non_default_only. It adds real semantics the bare schema lacks, e.g. relative vs absolute path matching.

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 specific verb and resource ('Read many parameter values at once, matched by name or label substring') and immediately distinguishes itself from siblings: it is 'the batch counterpart of set_parameters' and returns live values rather than 'the defaults for its type' like get_node_card. An agent can select it 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 routes the agent: use `inside` instead of `node_path` for whole-network reads, use this over set_parameters for batching, and use it over get_node_card for live vs. default values. Provides concrete selection examples for value_contains and non_default_only.

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