Skip to main content
Glama

show_model

Read-only

Retrieve detailed information for a specific model including modelfile, parameters, template, capabilities, architecture, and quantization level.

Instructions

Show detailed information for a specific model: modelfile excerpt, parameters, template, capabilities, architecture details, quantization level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesModel name (e.g. "llama3.1:8b" or "forge:b6c1").

Implementation Reference

  • The async function showModel that executes the tool logic. It validates the 'name' argument via requireString, sends a POST request to Ollama's /api/show endpoint, and returns a structured result with modelfile excerpt, parameters, template, capabilities, details, model_info_keys, and modified_at.
    async function showModel(args) {
      const bad = requireString(args, 'name');
      if (bad) return errorResult(bad);
      const r = await httpRequest('POST', '/api/show', { name: args.name });
      if (r.error) return errorResult(r.error);
      const d = r.data || {};
      return textResult({
        name: args.name,
        modelfile_excerpt: typeof d.modelfile === 'string' ? d.modelfile.slice(0, 500) : null,
        parameters: d.parameters || null,
        template: d.template || null,
        capabilities: d.capabilities || [],
        details: d.details || null,
        model_info_keys: d.model_info ? Object.keys(d.model_info).slice(0, 30) : [],
        modified_at: d.modified_at || null,
      });
    }
  • The input schema definition for the show_model tool, including the 'name' property (string, required) and a description explaining it shows modelfile excerpt, parameters, template, capabilities, architecture details, and quantization level.
    {
      name: 'show_model',
      description: 'Show detailed information for a specific model: modelfile excerpt, parameters, template, capabilities, architecture details, quantization level.',
      annotations: { title: 'Show model details', readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Model name (e.g. "llama3.1:8b" or "forge:b6c1").' },
        },
        required: ['name'],
        additionalProperties: false,
      },
  • server.js:385-394 (registration)
    The HANDLERS mapping that registers the show_model tool name to the showModel handler function, enabling dispatch when a tools/call request arrives with name 'show_model'.
    const HANDLERS = {
      ollama_status: ollamaStatus,
      list_models: listModels,
      list_running: listRunning,
      show_model: showModel,
      generate: generate,
      chat: chat,
      pull_model: pullModel,
      delete_model: deleteModel,
    };
  • server.js:274-306 (registration)
    The TOOLS array that defines the show_model tool metadata (name, description, annotations, inputSchema) for the tools/list response. The show_model entry is at lines 294-306.
    // ─── Tool registry ────────────────────────────────────────────────────────
    const TOOLS = [
      {
        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 },
      },
      {
        name: 'list_models',
        description: 'List locally-installed models: name, size in bytes, digest, modified timestamp, family (e.g. llama), parameter size (e.g. 8.0B), and quantization level (e.g. Q4_K_M).',
        annotations: { title: 'List installed models', readOnlyHint: true, destructiveHint: false, openWorldHint: false },
        inputSchema: { type: 'object', properties: {}, additionalProperties: false },
      },
      {
        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 },
      },
      {
        name: 'show_model',
        description: 'Show detailed information for a specific model: modelfile excerpt, parameters, template, capabilities, architecture details, quantization level.',
        annotations: { title: 'Show model details', readOnlyHint: true, destructiveHint: false, openWorldHint: false },
        inputSchema: {
          type: 'object',
          properties: {
            name: { type: 'string', description: 'Model name (e.g. "llama3.1:8b" or "forge:b6c1").' },
          },
          required: ['name'],
          additionalProperties: false,
        },
      },
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 context about the returned content but does not disclose additional behaviors like rate limits or authentication needs beyond what annotations provide.

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, well-structured sentence that immediately states the tool's purpose and lists key details without any fluff.

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?

Given the simple input (one parameter), good annotations, and no output schema, the description adequately explains the return content (modelfile excerpt, parameters, etc.), making it fairly complete for an agent to understand what the tool returns.

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 coverage is 100% and the schema already describes the 'name' parameter with an example. The description does not add additional meaning for the parameter beyond what the schema provides.

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 the tool shows detailed information for a specific model and enumerates the types of details (modelfile, parameters, etc.), distinguishing it from siblings like list_models.

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 context makes it clear that this tool is for retrieving details on a single model versus listing all models (list_models) or chatting (chat), but no explicit when-not or alternative names are provided.

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