Skip to main content
Glama
playcanvas

PlayCanvas Editor MCP Server

Official
by playcanvas

modify_entities

Edit properties of one or more entities in real-time 3D web applications using dot notation for nested property paths, enabling precise adjustments within the PlayCanvas Editor environment.

Instructions

Modify one or more entity's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
editsYesAn array of objects containing the ID of the entity to modify, the path to the property to modify, and the value to set the property to.

Implementation Reference

  • Handler function for the 'modify_entities' tool. It receives the 'edits' parameter and forwards it to the WebSocket server via wss.call('entities:modify', edits).
    ({ edits }) => {
        return wss.call('entities:modify', edits);
    }
  • Input schema for the 'modify_entities' tool, defining an array of edits with entity ID, property path, and new value.
    {
        edits: z.array(z.object({
            id: EntityIdSchema,
            path: z.string().describe('The path to the property to modify. Use dot notation to access nested properties.'),
            value: z.any().describe('The value to set the property to.')
        })).nonempty().describe('An array of objects containing the ID of the entity to modify, the path to the property to modify, and the value to set the property to.')
    },
  • Registration of the 'modify_entities' tool using mcp.tool(), including name, description, input schema, and handler function.
    mcp.tool(
        'modify_entities',
        'Modify one or more entity\'s properties',
        {
            edits: z.array(z.object({
                id: EntityIdSchema,
                path: z.string().describe('The path to the property to modify. Use dot notation to access nested properties.'),
                value: z.any().describe('The value to set the property to.')
            })).nonempty().describe('An array of objects containing the ID of the entity to modify, the path to the property to modify, and the value to set the property to.')
        },
        ({ edits }) => {
            return wss.call('entities:modify', edits);
        }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't mention permissions required, whether modifications are reversible, rate limits, error conditions, or what happens when modifying non-existent properties. For a mutation tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a tool with a clear primary function.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after modification, error handling, permissions needed, or how it differs from similar sibling tools. The context demands more comprehensive guidance than provided.

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?

The description mentions 'properties' which aligns with the 'edits' parameter in the schema, but adds no additional semantic context beyond what the 100% schema coverage already provides. The schema fully documents the structure, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('modify') and resource ('one or more entity's properties'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'reparent_entity' or 'set_script_text' which also modify entities in different ways, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'modify_scene_settings', 'set_material_diffuse', and 'reparent_entity' that also perform modifications, there's no indication of when this general-purpose entity property modifier is appropriate versus more specialized tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/playcanvas/editor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server