Skip to main content
Glama

ollama_status

Read-only

Check the reachability of the Ollama server and retrieve its version, enabling you to confirm connectivity before using other tools.

Instructions

Health check: whether the Ollama server is reachable and its version. Use this as a precondition before other tools if you're unsure whether Ollama is running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The ollamaStatus function that implements the 'ollama_status' tool. It performs a health check by making GET requests to '/' and '/api/version' endpoints, returning whether the server is reachable, the root message, and the Ollama version.
    async function ollamaStatus() {
      const root = await httpRequest('GET', '/');
      if (root.error) return errorResult(root.error);
      const ver = await httpRequest('GET', '/api/version');
      return textResult({
        url: OLLAMA_URL,
        reachable: true,
        root_message: root.text || (root.data ? JSON.stringify(root.data) : ''),
        version: ver.data?.version || null,
      });
    }
  • server.js:277-281 (registration)
    Tool registration entry for 'ollama_status' in the TOOLS array, defining its name, description, annotations, and input schema (no parameters needed).
      name: 'ollama_status',
      description: 'Health check: whether the Ollama server is reachable and its version. Use this as a precondition before other tools if you\'re unsure whether Ollama is running.',
      annotations: { title: 'Ollama server status', readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      inputSchema: { type: 'object', properties: {}, additionalProperties: false },
    },
  • server.js:386-386 (registration)
    The HANDLERS mapping that connects the tool name 'ollama_status' to the ollamaStatus function for dispatch.
    ollama_status: ollamaStatus,
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it checks reachability and version, providing modest context beyond annotations. No contradiction.

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?

Two sentences: first states purpose, second provides usage guidance. Every sentence is necessary and front-loaded. No wasted words.

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

Completeness4/5

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

For a simple parameterless tool with no output schema, the description covers the core function and precondition usage. It is complete enough given the simplicity.

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?

There are 0 parameters, so baseline is 4. Schema coverage is 100%, and description adds no further parameter details, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Health check: whether the Ollama server is reachable and its version,' which is a specific verb and resource. It clearly differentiates from sibling tools like list_models or chat by focusing on server availability.

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

Usage Guidelines5/5

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

The description explicitly says 'Use this as a precondition before other tools if you're unsure whether Ollama is running,' giving clear when-to-use guidance and context.

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/LukeLamb/claude-ollama-mcp'

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