Skip to main content
Glama

delete_component

Remove a specific component from Sketchup by its unique ID, enabling precise control over 3D models and scene adjustments within the SketchupMCP integration with Claude AI.

Instructions

Delete a component by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Handler function for the 'delete_component' MCP tool. It forwards the delete request to the SketchUp extension via JSON-RPC over socket, using the provided component ID.
    @mcp.tool()
    def delete_component(
        ctx: Context,
        id: str
    ) -> str:
        """Delete a component by ID"""
        try:
            sketchup = get_sketchup_connection()
            result = sketchup.send_command(
                method="tools/call",
                params={
                    "name": "delete_component",
                    "arguments": {"id": id}
                },
                request_id=ctx.request_id
            )
            return json.dumps(result)
        except Exception as e:
            return f"Error deleting component: {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. While 'Delete' implies a destructive operation, the description doesn't specify whether deletion is permanent or reversible, what happens to dependent elements, or what permissions are required. For a destructive tool with zero annotation coverage, this is a significant gap in behavioral context.

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 extremely concise at just four words, front-loading the essential information with zero wasted language. Every word earns its place in communicating the core functionality.

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 destructive operation with no annotations, no output schema, and 0% schema description coverage, the description is insufficiently complete. It doesn't address critical aspects like deletion consequences, error conditions, return values, or parameter validation that an agent needs to use this tool effectively.

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%, meaning the single parameter 'id' has no documentation in the schema. The description mentions 'by ID' which provides minimal context about the parameter's purpose, but doesn't explain what format the ID should be, where to find it, or any validation rules. This doesn't adequately compensate for the complete lack of schema documentation.

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 action ('Delete') and target resource ('a component by ID'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'create_component' or 'transform_component', but the verb+resource combination is specific enough for basic understanding.

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 about when to use this tool versus alternatives like 'transform_component' or when deletion is appropriate versus other operations. The description only states what the tool does, not when it should be selected among available options.

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