Skip to main content
Glama

set_material

Assign a specific material to a component in Sketchup using the SketchupMCP integration, enabling precise control over 3D model appearances directly through Claude AI.

Instructions

Set material for a component

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
materialYes

Implementation Reference

  • The handler function for the 'set_material' MCP tool. It is decorated with @mcp.tool() for registration and forwards the material setting request to the Sketchup extension via JSON-RPC.
    @mcp.tool()
    def set_material(
        ctx: Context,
        id: str,
        material: str
    ) -> str:
        """Set material for a component"""
        try:
            sketchup = get_sketchup_connection()
            result = sketchup.send_command(
                method="tools/call",
                params={
                    "name": "set_material",
                    "arguments": {
                        "id": id,
                        "material": material
                    }
                },
                request_id=ctx.request_id
            )
            return json.dumps(result)
        except Exception as e:
            return f"Error setting material: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('Set'), but fails to describe critical traits such as required permissions, whether the operation is reversible, potential side effects (e.g., if it affects other components), or error handling. This is a significant gap for a mutation tool with zero annotation coverage.

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 with zero wasted words. It is appropriately sized for a simple tool and front-loaded with the core action, making it easy to parse quickly.

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 complexity (a mutation tool with no annotations, no output schema, and 0% schema coverage), the description is incomplete. It lacks details on behavior, parameter usage, and expected outcomes, which are essential for an agent to invoke the tool correctly. The conciseness does not compensate for these substantive gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters. It mentions 'material for a component', which hints at the 'material' parameter's purpose, but provides no details on format, constraints, or examples. The 'id' parameter is entirely undocumented. With two required parameters and no schema descriptions, the description adds minimal value beyond the bare schema.

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

Purpose3/5

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

The description states the action ('Set') and resource ('material for a component'), which provides a basic understanding of the tool's function. However, it lacks specificity about what 'material' means in this context (e.g., physical properties, visual appearance, or structural attributes) and doesn't distinguish it from sibling tools like 'transform_component' or 'create_component', which might also involve material-related operations.

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. The description does not mention prerequisites (e.g., whether the component must exist), exclusions, or comparisons to sibling tools like 'create_component' (which might set initial material) or 'transform_component' (which might modify other properties). This leaves the agent without context for tool selection.

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/BearNetwork-BRNKC/SketchUp-MCP'

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