Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

delete_component

Deletes a SketchUp component by ID or name so MCP clients can remove a specific scene element.

Instructions

Borra componente por id o nombre.

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": {
      "id_or_name": "<id_or_name>"
    },
    "name": "delete_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about irreversibility, undo availability, whether child/nested entities are removed, or what happens when the id/name does not resolve. For a destructive mutation this is a substantial disclosure gap.

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?

A single short sentence with the action and target selector front-loaded and no filler. Its brevity is appropriate in form, even though the content is thin.

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?

An output schema exists, so return values need not be explained, but a destructive, unannotated tool with a completely undocumented parameter needs far more than one line. Missing are deletion scope, failure modes, and reversibility information an agent needs before invoking it.

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% and the single parameter is documented nowhere. The phrase "por id o nombre" merely restates the parameter name id_or_name without clarifying accepted formats, name-matching rules, ambiguity handling, or error behavior for unknown targets, so it adds essentially no meaning beyond the schema.

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?

States a specific verb and resource ("Borra componente") plus the lookup key ("por id o nombre"), so an agent knows exactly what action is performed and how the target is addressed. It does not differentiate itself from siblings such as clear_scene or transform_component, which is the only thing keeping it from a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives for removing objects (e.g. clear_scene for bulk removal). The only implicit signal is that a single component is targeted, which the agent must infer from the singular noun.

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