Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

material_apply

Apply a material to an actor's mesh component by asset path, optionally targeting a specific slot or component. Returns validation.

Instructions

Apply a material to an actor's mesh component. Returns validation by default.

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": {
      "actor_name": "<actor_name>",
      "material_path": "<material_path>"
    },
    "name": "material_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
slot_nameNoMaterial slot name (overrides slot_index if both provided)
actor_nameYesLabel of the target actor
slot_indexNoMaterial slot index (default 0)
material_pathYesAsset path of the material to apply
component_nameNoSpecific mesh component name (default: first mesh found)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions 'Returns validation by default' but that is ambiguous—what validation? It does not state that this mutates the actor, whether the change is reversible, or whether it overrides the existing material. The description is too minimal to provide adequate transparency.

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

Conciseness5/5

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

The description is one short, front-loaded sentence followed by a brief note on return behavior. No wasted words, easily scannable.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what 'validation' means, what happens with default slot selection, preconditions like valid material paths, or the mutating nature of the operation. This is a significant gap for a non-trivial 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 description coverage is 100%, so parameters are fully described in the schema itself. The description adds no additional parameter context. Baseline of 3 is appropriate since the schema carries the semantic load.

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?

The description clearly states the tool's action: 'Apply a material to an actor's mesh component.' This is a specific verb (apply) and resource (material, actor's mesh component), distinguishing it from related tools like material_create (creating materials) or material_info (inspecting materials).

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?

No guidance is provided on when to use this tool versus alternatives such as material_create or material_instance_set_params. The usage intention is only implied by the verb 'apply', with no explicit context or exclusions.

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