Skip to main content
Glama
NightTrek

Ollama MCP Server

by NightTrek

pull

Download AI models from registries to run locally with Ollama's MCP server, enabling local LLM management and integration.

Instructions

Pull a model from a registry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the model to pull

Implementation Reference

  • The handler function that executes the 'ollama pull' command using the provided model name and returns the command's output as text content.
    private async handlePull(args: any) {
      try {
        const { stdout, stderr } = await execAsync(`ollama pull ${args.name}`);
        return {
          content: [
            {
              type: 'text',
              text: stdout || stderr,
            },
          ],
        };
      } catch (error) {
        throw new McpError(ErrorCode.InternalError, `Failed to pull model: ${formatError(error)}`);
      }
    }
  • The input schema defining the 'name' parameter required for the 'pull' tool.
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Name of the model to pull',
        },
      },
      required: ['name'],
      additionalProperties: false,
    },
  • src/index.ts:264-265 (registration)
    The switch case that registers and dispatches 'pull' tool calls to the handlePull method.
    case 'pull':
      return await this.handlePull(request.params.arguments);
  • src/index.ts:134-148 (registration)
    The tool definition registered in the ListTools response, including name, description, and schema.
    {
      name: 'pull',
      description: 'Pull a model from a registry',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the model to pull',
          },
        },
        required: ['name'],
        additionalProperties: false,
      },
    },
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 of behavioral disclosure. It states the action but doesn't explain what 'pull' entails—such as whether it downloads, caches, or modifies data, requires authentication, has side effects, or handles errors. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to grasp quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like what happens after pulling (e.g., where the model is stored, success/failure indicators) or usage context, which is insufficient for a tool that likely involves network operations or data handling.

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 input schema has 100% description coverage, with the 'name' parameter documented as 'Name of the model to pull'. The description adds no additional meaning beyond this, so it meets the baseline score of 3 for high schema coverage without extra param info.

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 clearly states the action ('pull') and resource ('a model from a registry'), making the purpose understandable. However, it doesn't differentiate this tool from its siblings like 'push', 'list', or 'rm', which likely operate on similar resources, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for pulling models, or when to choose other tools like 'push' or 'list', leaving usage ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NightTrek/Ollama-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server