Skip to main content
Glama

list_running

Read-only

List models currently loaded in VRAM with their size, VRAM footprint, and expiry timestamp to determine if Ollama is idle.

Instructions

List models currently loaded into VRAM with their size, VRAM footprint, and expiry timestamp. Empty list means Ollama is idle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_running' tool. Makes a GET request to /api/ps to list models currently loaded in VRAM, returning name, size, VRAM footprint, and expiry timestamp.
    async function listRunning() {
      const r = await httpRequest('GET', '/api/ps');
      if (r.error) return errorResult(r.error);
      const models = (r.data?.models || []).map((m) => ({
        name: m.name,
        size_bytes: m.size,
        size_vram_bytes: m.size_vram,
        expires_at: m.expires_at,
        digest: m.digest,
      }));
      return textResult({ count: models.length, models });
    }
  • The tool schema/definition for 'list_running', including its description, annotations, and input schema (empty object, no params needed).
    {
      name: 'list_running',
      description: 'List models currently loaded into VRAM with their size, VRAM footprint, and expiry timestamp. Empty list means Ollama is idle.',
      annotations: { title: 'List running models', readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      inputSchema: { type: 'object', properties: {}, additionalProperties: false },
    },
  • server.js:388-388 (registration)
    The tool-to-handler mapping registering 'list_running' to the listRunning function.
    list_running: listRunning,
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral details about the output fields (size, VRAM footprint, expiry timestamp) and the meaning of an empty list.

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 with zero wasted words. Front-loaded with the core purpose followed by additional context about the empty list scenario.

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

Completeness5/5

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

Given zero parameters, no output schema, but with annotations present, the description fully explains the tool's purpose, output content, and significance of an empty result. No gaps.

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 no parameters, so the description cannot add information beyond the schema. Baseline of 4 is appropriate as the description focuses on output rather than parameters.

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 clearly states it lists models loaded into VRAM with specific attributes (size, VRAM footprint, expiry timestamp), which is distinct from sibling tools like list_models (likely all models) and ollama_status (general status).

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

Usage Guidelines4/5

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

The description implies when to use (to see running models) and provides context that an empty list means Ollama is idle. It does not explicitly mention alternatives but sibling names provide differentiation.

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