Skip to main content
Glama
hyzhak

Ollama MCP Server

by hyzhak

Create model (remote only supports 'from')

create

Create custom AI models from existing base models using the Ollama MCP Server to run and manage local AI with privacy.

Instructions

Create a model from a base model (remote only, no Modelfile support)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
fromYes

Implementation Reference

  • The handler function for the "create" tool. It takes 'name' and 'from' parameters, calls ollama.create to create a new model from the base model specified in 'from', and returns the JSON result or an error message.
    async ({ name, from }) => {
      try {
        const result = await ollama.create({ model: name, from });
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      } catch (error) {
        return { content: [{ type: "text", text: `Error: ${formatError(error)}` }], isError: true };
      }
    }
  • Input schema for the "create" tool, defining required string parameters 'name' (new model name) and 'from' (base model).
    inputSchema: { name: z.string(), from: z.string() },
  • src/index.ts:65-80 (registration)
    Registration of the "create" tool using server.registerTool, including title, description, input schema, and handler function.
    server.registerTool(
      "create",
      {
        title: "Create model (remote only supports 'from')",
        description: "Create a model from a base model (remote only, no Modelfile support)",
        inputSchema: { name: z.string(), from: z.string() },
      },
      async ({ name, from }) => {
        try {
          const result = await ollama.create({ model: name, from });
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text", text: `Error: ${formatError(error)}` }], isError: true };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'remote only' and 'no Modelfile support', which adds some context about limitations, but fails to describe critical behaviors like whether this is a mutating operation, what permissions are required, error handling, or what the response looks like. For a creation tool with zero annotation coverage, this leaves significant gaps.

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 extremely concise—a single sentence that efficiently conveys the core action and key constraints. Every word earns its place, with no wasted text, making it easy to parse 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 complexity of a model creation tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavioral traits, parameter usage, error conditions, and return values, leaving the agent with insufficient information to use the tool effectively beyond basic intent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'from a base model', which hints at the 'from' parameter's purpose, but doesn't explain the 'name' parameter or provide any details on format, constraints, or examples. This adds minimal value beyond what the bare schema provides.

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 ('create a model') and specifies the resource ('from a base model'), which distinguishes it from other creation-like tools. However, it doesn't explicitly differentiate from all sibling tools like 'pull' or 'run' that might also involve model creation in some contexts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context with 'remote only, no Modelfile support', suggesting this tool is for remote operations without local configuration. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'pull' or 'run', nor does it mention prerequisites or exclusions beyond the remote-only constraint.

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/hyzhak/ollama-mcp-server'

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