Skip to main content
Glama

get_mpci_info

Read-onlyIdempotent

Read a Material Parameter Collection Instance's scalar and vector parameter values on the editor or a live world to inspect overrides, without changing any value.

Instructions

Read the transient Material Parameter Collection Instance of one collection on a world (editor by default): instance_exists, is_valid, parent_collection_path and, per parameter, current_value or current_rgba with readback_ok. Changes no value, but the engine lookup creates the instance, at the collection defaults, when the world has none, so instance_exists is true in practice; scalar_override_count and vector_override_count are only the parameter counts.

Returns: { collection_path: string, world_name: string, instance_exists: bool, is_valid: bool, parent_collection_path: string, scalar_override_count: int, vector_override_count: int, scalars: [object], vectors: [object] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
world_labelNoEmpty or "editor" for the editor world (the default); otherwise the UWorld name of a live world context, compared case-insensitively
collection_pathYesFull /Game path of the parent MPC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / world_label / description
      Previous value: -"Optional world context label, default editor"New value: +"Empty or \"editor\" for the editor world (the default); otherwise the UWorld name of a live world context, compared case-insensitively"
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Discloses a non-obvious side effect beyond the readOnly/idempotent annotations: the engine lookup itself creates the instance at collection defaults when none exists, so instance_exists is effectively always true. It also clarifies that the override counts are only parameter counts, preventing a misread. This is exactly the kind of context annotations cannot carry.

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?

Purpose is front-loaded and the Returns block usefully compensates for the absent output schema. The second sentence is dense and semicolon-chained, but each clause carries real behavioral information rather than filler.

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?

With no output schema, the inline Returns object fully describes the response shape (fields and per-parameter scalars/vectors). Combined with the annotation safety profile and the side-effect disclosure, an agent has everything needed to call and interpret this tool.

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 coverage is 100%, so both parameters are already documented. The description restates the 'world (editor by default)' default and the one-collection scope but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 precise verb (Read) and an exact resource: the transient Material Parameter Collection Instance of one collection on a world. The word 'transient' plus 'Instance' distinguishes it from the collection-asset siblings (get_collection_info, get_collection_param_info) without opening their schemas.

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?

The '(editor by default)' note gives context on the default world target, but the description never states when to reach for this tool versus get_collection_info or the set_mpci_* siblings, nor any prerequisites. Usage is only implied by the readback framing.

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