Skip to main content
Glama

mcp_ollama_status

Check the status of Ollama servers connected to the Ontology MCP, enabling real-time monitoring of AI models for ontology data querying and manipulation.

Instructions

Ollama 서버 상태 확인

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYesDummy parameter for no-parameter tools

Implementation Reference

  • Complete tool definition for 'mcp_ollama_status' including input schema, description, and handler function. The handler delegates to ollamaService.getStatus() and formats the response.
    {
      name: 'mcp_ollama_status',
      description: 'Ollama 서버 상태 확인',
      inputSchema: {
        type: 'object',
        properties: {
          random_string: {
            type: 'string',
            description: 'Dummy parameter for no-parameter tools'
          }
        },
        required: ['random_string']
      },
      async handler(args: any): Promise<ToolResponse> {
        try {
          const result = await ollamaService.getStatus();
          return {
            content: [{
              type: 'text',
              text: result
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `Status 확인 오류: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    },
  • Core implementation of Ollama status check in OllamaService.getStatus(). Executes 'ollama list' command and queries /api/tags endpoint to determine server status and list models.
    /**
     * Ollama 상태 확인
     */
    async getStatus(): Promise<string> {
      try {
        // 로컬 Ollama 목록 커맨드 실행
        const { stdout, stderr } = await execAsync('ollama list');
        if (stderr) {
          throw new Error(stderr);
        }
        
        // 설치된 모델 가져오기
        const response = await axios.get(this.getApiUrl('tags'));
        
        return JSON.stringify({
          status: 'online',
          localModels: stdout.trim(),
          apiModels: response.data
        }, null, 2);
      } catch (error) {
        return JSON.stringify({
          status: 'offline',
          error: formatError(error)
        }, null, 2);
      }
    }
  • src/index.ts:26-54 (registration)
    MCP Server capabilities registration enabling the 'mcp_ollama_status' tool (line 37).
      mcp_sparql_execute_query: true,
      mcp_sparql_update: true,
      mcp_sparql_list_repositories: true,
      mcp_sparql_list_graphs: true,
      mcp_sparql_get_resource_info: true,
      mcp_ollama_run: true,
      mcp_ollama_show: true,
      mcp_ollama_pull: true,
      mcp_ollama_list: true,
      mcp_ollama_rm: true,
      mcp_ollama_chat_completion: true,
      mcp_ollama_status: true,
      mcp_http_request: true,
      mcp_openai_chat: true,
      mcp_openai_image: true,
      mcp_openai_tts: true,
      mcp_openai_transcribe: true,
      mcp_openai_embedding: true,
      mcp_gemini_generate_text: true,
      mcp_gemini_chat_completion: true,
      mcp_gemini_list_models: true,
      mcp_gemini_generate_images: false,
      mcp_gemini_generate_image: false,
      mcp_gemini_generate_videos: false,
      mcp_gemini_generate_multimodal_content: false,
      mcp_imagen_generate: false,
      mcp_gemini_create_image: false,
      mcp_gemini_edit_image: 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 tool checks server status, implying a read-only operation, but doesn't disclose any behavioral traits such as what 'status' includes (e.g., uptime, version, health), whether it requires authentication, rate limits, or what the response looks like. This leaves significant gaps for an agent to understand how to use it effectively.

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 with a single phrase 'Ollama 서버 상태 확인', which is front-loaded and wastes no words. Every part of the sentence directly contributes to stating the tool's purpose, making it efficient and well-structured for its minimal content.

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 low complexity (a status check with a dummy parameter) and no annotations or output schema, the description is incomplete. It doesn't explain what 'status' entails, how results are returned, or any prerequisites, leaving the agent with insufficient context to use the tool effectively. While concise, it lacks necessary details for full understanding.

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?

The input schema has 1 parameter with 100% description coverage, documenting it as a 'Dummy parameter for no-parameter tools'. The description adds no parameter information beyond this, but since the schema fully covers the parameter and it's a dummy parameter, the baseline is high. With 0 meaningful parameters, the description doesn't need to compensate, making a score of 4 appropriate as it doesn't detract from the schema's clarity.

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

Purpose3/5

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

The description 'Ollama 서버 상태 확인' (Ollama server status check) states the tool's purpose clearly with a specific verb ('확인' - check) and resource ('Ollama 서버' - Ollama server). However, it doesn't distinguish this from sibling tools like 'mcp_ollama_list' or 'mcp_ollama_show', which might also provide status-related information. The purpose is understandable but lacks sibling differentiation.

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. There's no mention of when it should be used (e.g., for health checks, before other operations) or when not to use it, nor does it reference any sibling tools like 'mcp_ollama_list' that might serve similar purposes. Usage is implied by the name but not explicitly stated.

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