Skip to main content
Glama

mcp_ollama_pull

Download models from the Ollama registry to integrate with Ontology MCP, enabling AI-driven querying and manipulation of ontology data via SPARQL endpoints.

Instructions

Ollama 레지스트리에서 모델을 다운로드합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes다운로드할 모델 이름

Implementation Reference

  • MCP tool handler function that invokes ollamaService.pullModel and returns the result as ToolResponse.
    async handler(args: any): Promise<ToolResponse> {
      const result = await ollamaService.pullModel(args);
      return {
        content: [
          {
            type: 'text' as const,
            text: result
          }
        ]
      };
  • Input schema for mcp_ollama_pull tool requiring a model name.
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: '다운로드할 모델 이름'
        }
      },
      required: ['name']
    },
  • src/index.ts:33-33 (registration)
    Tool listed in MCP server capabilities for availability declaration.
    mcp_ollama_pull: true,
  • Core helper function in OllamaService that handles the actual model pull via Ollama API with streaming response.
    async pullModel(args: { name: string }): Promise<string> {
      try {
        const response = await axios.post(
          this.getApiUrl('pull'),
          {
            name: args.name,
          },
          {
            responseType: 'stream',
          }
        );
    
        // 다운로드 진행 상황을 텍스트로 수집
        let result = '';
        for await (const chunk of response.data) {
          result += chunk.toString();
        }
        return result;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new McpError(
            ErrorCode.InternalError,
            `Ollama API 오류: ${error.response?.data?.error || error.message}`
          );
        }
        throw new McpError(ErrorCode.InternalError, `모델 다운로드에 실패했습니다: ${formatError(error)}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool downloads a model but lacks critical behavioral details: it doesn't specify if this is a network-intensive operation, whether it requires authentication, what happens if the model already exists, or what the output looks like (e.g., success/failure status). For a download tool with zero annotation coverage, this is a significant gap.

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 in Korean that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every part contributing essential information.

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 tool's complexity (a download operation with potential network/authentication implications), no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like error handling, performance, or return values, leaving the agent with insufficient context for reliable use.

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%, with the single parameter 'name' documented as '다운로드할 모델 이름' (model name to download). The description doesn't add meaning beyond this, such as format examples or constraints (e.g., case sensitivity). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('다운로드합니다' - downloads) and resource ('모델' - model) from 'Ollama 레지스트리' (Ollama registry). It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like mcp_ollama_list or mcp_ollama_run, which prevents a perfect 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing model name), exclusions, or comparisons to siblings like mcp_ollama_list (for listing models) or mcp_ollama_run (for running models).

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

Related 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/bigdata-coss/agent_mcp'

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