Skip to main content
Glama
MCP Ollama Server

MCP Ollama Server

by MikeyBeez

ollama_embeddings

Converts text prompts into vector embeddings using an Ollama model to power semantic search, similarity comparisons, and retrieval workflows.

Instructions

Generate embeddings using an Ollama model

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": {
      "prompt": "<prompt>"
    },
    "name": "ollama_embeddings"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel name (must support embeddings)nomic-embed-text
promptYesText to generate embeddings for

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 behavioral burden and discloses almost nothing. It does not say that the Ollama server must be running, that the named model must already be pulled locally (a common failure mode for Ollama), whether the call is local/remote, or what the response contains.

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 short sentence with no filler and the key concept front-loaded. It is efficient, though the terseness comes at the cost of information rather than being trim of redundancy.

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?

The tool is simple (2 params, 1 required, no nested objects), but with no output schema the description should at least indicate that the return value is a numeric embedding vector. It also omits the prerequisite that a compatible embedding model must be available, which is the main way this call fails.

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 schema already documents both the optional model (with a default) and the required prompt text. The description adds no meaning beyond that, so the baseline of 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?

The description names a specific verb ('Generate') and resource ('embeddings') plus the provider ('Ollama model'), which is enough to separate it from ollama_chat and ollama_generate. It stops short of explicitly contrasting itself with those siblings, so it does not reach 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 or when-not-to-use guidance, no mention that this is for vector/similarity work rather than text generation, and no hint about when to prefer ollama_generate or ollama_chat. The agent must infer all routing decisions.

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