Skip to main content
Glama
MCP Ollama Server

MCP Ollama Server

by MikeyBeez

ollama_delete

Deletes a specified Ollama model from local storage, helping free disk space and remove unused models.

Instructions

Delete a model from local storage

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>"
    },
    "name": "ollama_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel name to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for what is an irreversible mutation. "From local storage" usefully clarifies that only the local copy is affected (not the registry), but it never states that deletion is permanent, whether the call errors when the model is absent, or whether disk space is reclaimed.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though the terseness leaves no room for the risk information this destructive tool needs.

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 simple one-parameter tool the description covers the mechanics, but as a destructive operation with no annotations and no output schema, it should disclose irreversibility and error behavior. Those omissions are the gaps an agent would most need filled.

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?

The single parameter has 100% schema description coverage ("Model name to delete"), so the schema already does the work. The description adds no format hints, naming conventions, or tag/version syntax beyond that baseline.

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?

"Delete a model from local storage" states a specific verb (delete) and resource (model) plus the scope (local storage), which cleanly separates it from siblings like ollama_pull or ollama_list. It does not explicitly name or contrast those alternatives, so it stops short of 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?

There is no when-to-use guidance, no statement of prerequisites (e.g. the model must already be pulled), and no warning about when not to call it. An agent must infer the entire decision context from the name and the single sentence.

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