Skip to main content
Glama

project_remove_part

Remove a part from a user project and delete copied files no other part uses, while leaving the central store unchanged; pinned files remain by default.

Instructions

Remove a part from the user project, and delete its copies that no other part uses. A pinned file stays (see project_update_part), unless delete_pinned is true. The central store does not change, because other projects can use the part. To change the MPN of a part, use project_update_part. Gives the removed part and the deleted and kept files.

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": {
      "mpn": "<mpn>"
    },
    "name": "project_remove_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpnYesThe MPN of the project part.
pathNoA folder of the user project (default: the working folder of the server). The project file datasheet-lens.toml is in it or in a parent folder.
dry_runNoTrue: change nothing, only tell what would change.
manufacturerNoThe manufacturer, any of its names (TI or Texas Instruments: the store knows the names of one manufacturer). Necessary only when two parts have the same MPN. With a datasheet, the tool reads the manufacturer from it: a given name must be a name of the same manufacturer.
delete_pinnedNoTrue: also delete a pinned file (pinned = true: a file outside the subfolder of the layout of its part, or a file that project_update_part pinned).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / manufacturer / description
      Previous value: -"The manufacturer, any of its names (TI or Texas Instruments: the store knows the names of one manufacturer). Necessary only when two parts have the same MPN."New value: +"The manufacturer, any of its names (TI or Texas Instruments: the store knows the names of one manufacturer). Necessary only when two parts have the same MPN. With a datasheet, the tool reads the manufacturer from it: a given name must be a name of the same manufacturer."
  2. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / delete_pinned / description
      Previous value: -"True: also delete a file that the user put into the project folder (pinned = true)."New value: +"True: also delete a pinned file (pinned = true: a file outside the subfolder of the layout of its part, or a file that project_update_part pinned)."
  3. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / manufacturer / description
      Previous value: -"The manufacturer, for example TI. Necessary only when two parts have the same MPN."New value: +"The manufacturer, any of its names (TI or Texas Instruments: the store knows the names of one manufacturer). Necessary only when two parts have the same MPN."
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that copies unused by other parts are deleted, that pinned files are protected by default, and that the central store is untouched because other projects may use the part. It also states what is returned (removed part, deleted and kept files). It omits any warning about irreversibility of the deletions and never mentions the dry_run escape hatch.

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?

Four short sentences with the destructive action front-loaded and no filler; the conditional pinned-file rule follows immediately. The clause explaining why the central store is unchanged is slightly verbose but still informative rather than redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive five-parameter mutation tool with no annotations, the description covers the key semantics: what gets deleted, what is protected, what is untouched, and that results are returned (an output schema also exists). The remaining gap is the absence of any mention of dry_run or permission/auth requirements an agent should know about before invoking a destructive call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning about the delete_pinned interaction ('a pinned file stays ... unless delete_pinned is true') beyond the field-level definition. It does not add anything for mpn, path, manufacturer, or dry_run, leaving those entirely to the schema.

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?

States a specific verb and resource ('Remove a part from the user project') plus the consequential side effect ('delete its copies that no other part uses'), and explicitly names project_update_part as the tool for a different operation (MPN changes). An agent can distinguish this from project_add_part or project_update_part without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete routing guidance: use project_update_part to change an MPN, and expect a pinned file to survive unless delete_pinned is set. It does not spell out when removal is inappropriate (e.g. before/after sync) or mention dry_run as the safe alternative, but the positive when-to-use and conditional rules are clear.

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