Skip to main content
Glama
MCP Ollama Server

MCP Ollama Server

by MikeyBeez

ollama_list

Lists available Ollama models so you can see which local models are ready for inference, chat, or embedding tasks.

Instructions

List available Ollama models

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ollama_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say whether the result covers locally pulled models, remote registry models, or loaded/running models, nor whether an Ollama server must be reachable, nor the shape of the response.

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 clause with no filler. Nothing is wasted, though there is also very little substance beyond the name restated in plain English.

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

Completeness3/5

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

A no-parameter list tool is simple, but with no output schema the description should at least indicate what comes back (model names, tags, sizes) and whether it reflects local versus remote availability. Without that, an agent cannot predict the return value.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; baseline applies. The 100% schema coverage is trivial for an empty object.

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?

States a specific verb ('List') and resource ('Ollama models'), so the agent knows this retrieves the model inventory. It does not distinguish itself from sibling ollama_info, which presumably returns details for a single model, leaving the boundary between 'list' and 'info' implicit.

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?

No guidance on when to call this versus ollama_info, ollama_pull, or the generation tools. The agent must infer that this is the discovery step preceding a call that requires a model name.

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