Skip to main content
Glama
MCP Ollama Server

MCP Ollama Server

by MikeyBeez

ollama_pull

Pull a specified model from the Ollama registry to make it available for local AI inference and chat.

Instructions

Pull/download a model from Ollama registry

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_pull"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel name to pull (e.g., llama3.2, mistral)

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?

No annotations are supplied, so the description carries the full burden and largely fails it: it doesn't disclose that this is a network-bound, long-running download that writes model weights to local disk, that it may take minutes or emit progress output, or what happens when the model name is invalid or already present.

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 front-loaded sentence with no filler or repetition. It is efficient, though its brevity reflects under-specification rather than deliberate density.

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 one-parameter mutation-like tool with no annotations and no output schema, the description should at minimum convey the long-running download semantics and expected outcome. As written it leaves the agent unable to anticipate duration, disk effects, or failure modes.

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% and the single parameter includes an example (llama3.2, mistral), so the schema already does the documentation work. The description adds nothing about the model-name format (tag/quantization suffixes) beyond what the schema provides, so the baseline 3 applies.

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?

"Pull/download a model from Ollama registry" gives a specific verb (pull/download) and a specific resource (model from the Ollama registry), which is enough for an agent to separate it from ollama_list, ollama_delete or ollama_chat. It stops short of a 5 because it never names or contrasts with a sibling tool.

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 guidance on when to choose this over alternatives (e.g. ollama_list to check if the model is already present, or ollama_info to inspect it first). No prerequisites are stated either, such as needing the Ollama server reachable or sufficient disk space.

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