Skip to main content
Glama

remove_model

Destructive

Removes a user-added model link from ComfyUI without deleting the original file; ask for confirmation before calling with user_confirmed=true.

Instructions

Removes a model the user added (from list_models "added_by_user"). Only our link is removed, never the user's file. Ask the user first, then call with user_confirmed=true.

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": {
      "file": "<file>"
    },
    "name": "remove_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
user_confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds the materially important nuance that only the app's link is removed and never the user's underlying file, which changes how risky the call actually is. It also discloses the required user-confirmation protocol before invoking.

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?

Three short sentences, no filler, with the scope constraint and the confirmation requirement front-loaded where the agent will read them first.

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 two-parameter mutation with no output schema, the description covers effect scope and the safety protocol well. The remaining gap is the format/identity of the `file` value and any failure behavior, which an agent would still have to guess.

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?

Schema coverage is 0%, so the description carries the burden. It explains user_confirmed clearly (must be true after asking the user), but never clarifies what the `file` string should contain — a path, a model name, or an identifier from list_models — leaving the required parameter underspecified.

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?

"Removes a model the user added" states a specific verb and a scoped resource, and the parenthetical ties it to list_models filtered by "added_by_user", so an agent knows which subset of models this applies to. It does not explicitly distinguish itself from other removal siblings such as remove_audio, but the resource is unambiguous.

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 an explicit workflow prerequisite ("Ask the user first, then call with user_confirmed=true") and points to list_models with the "added_by_user" filter as the way to find valid targets. No when-not-to-use guidance is given, but the operational context is clear.

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