Skip to main content
Glama
Local AI MCP

Local AI MCP

Official
by TMHSDigital

Remove model

remove_model
Destructive

Permanently delete a model from one specified local AI provider; provider and confirmation are required to prevent accidental removal.

Instructions

DESTRUCTIVE: Permanently delete a model from one provider. provider is REQUIRED (no fan-out). If the client supports elicitation the user is asked to confirm directly; otherwise confirm:true is required.

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

Input Schema

NameRequiredDescriptionDefault
modelYesModel id/name to remove
confirmNoMust be true when the client cannot ask the user directly (no elicitation support)
providerYesProvider to delete from (required). Omit to let the server choose (local providers only, unless LOCAL_AI_ALLOW_HOSTED_FALLBACK is set).

Output Schema

NameRequiredDescriptionDefault
removeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to perform this destructive deletion"New value: +"Must be true when the client cannot ask the user directly (no elicitation support)"
    • changedInput schema / properties / provider / description
      Previous value: -"Required provider id (delete is scoped to a single provider)"New value: +"Provider to delete from (required). Omit to let the server choose (local providers only, unless LOCAL_AI_ALLOW_HOSTED_FALLBACK is set)."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "ollama",
      -  "lmstudio",
      -  "moonshot"
      -]New value: +[
      +  "ollama",
      +  "lmstudio",
      +  "llamacpp",
      +  "dockermodelrunner"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "model",
      -  "confirm",
      -  "provider"
      -]New value: +[
      +  "model",
      +  "provider"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "remove": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "remove"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent behavior, but the description adds useful operational detail about permanence and the confirmation flow. However, the claim that provider is REQUIRED (no fan-out) conflicts with the schema property text saying provider may be omitted to let the server choose, which weakens the behavioral guidance.

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 front-loaded with DESTRUCTIVE and is very compact. Every clause contributes either safety, required-parameter, or confirmation behavior, with no wasted text.

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?

With annotations covering safety and an output schema covering return values, the description supplies the key missing context: permanence and the confirmation/elicitation fallback. It would be more complete if it resolved the provider-optional conflict and explicitly contrasted remove_model with unload_model.

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 description coverage is 100%, so the schema already defines all three parameters. The description adds the no-fan-out requirement and clarifies confirmation behavior, but its provider-required claim conflicts with the provider property description that says omitting provider lets the server choose, making the added semantic value only partly reliable.

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?

The description states a specific destructive verb and resource: permanently delete a model from one provider. It also scopes the operation to a single provider and no fan-out, which helps distinguish it from broader or memory-only sibling operations such as unload_model.

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?

It gives clear usage context: this is destructive, provider is required, and confirmation is handled through elicitation or the confirm:true fallback. It does not explicitly name unload_model as the non-destructive alternative, so the when-not guidance is implied rather than stated.

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