Skip to main content
Glama

show_model

Read-only

Retrieve detailed information about an Ollama model, including its modelfile excerpt, 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 showModel function — the tool handler for 'show_model'. It validates the required 'name' argument, calls Ollama's POST /api/show endpoint, and returns model details (modelfile excerpt, parameters, template, capabilities, details, model_info_keys, 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,
      });
    }
  • Tool registration entry for 'show_model' in the TOOLS array, defining its description, annotations, and inputSchema (requires 'name' string).
    {
      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 object that registers the string 'show_model' to the showModel function for dispatch.
    const HANDLERS = {
      ollama_status: ollamaStatus,
      list_models: listModels,
      list_running: listRunning,
      show_model: showModel,
      generate: generate,
      chat: chat,
      pull_model: pullModel,
      delete_model: deleteModel,
    };
  • The textResult helper utility used by showModel to wrap JSON output in MCP's content format.
    function textResult(obj) {
      return { content: [{ type: 'text', text: JSON.stringify(obj, null, 2) }] };
    }
Behavior4/5

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

Annotations already indicate readOnlyHint=true, so the description does not need to restate safety. The description adds behavioral context by enumerating the types of information returned (parameters, template, etc.), which is helpful for understanding what the tool does beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with purpose and then lists details. No redundant information. Efficient without being too brief.

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 annotations (readOnlyHint) and simple input schema, the description adequately explains the tool's output without needing an output schema. It covers what the tool does and what it 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?

Input schema has 100% coverage for the single parameter 'name' with a clear description. The tool's description does not add additional semantic detail beyond what the schema provides, so baseline score of 3 is appropriate.

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 it shows detailed information for a specific model, listing the types of details (modelfile excerpt, parameters, etc.). It implicitly differentiates from sibling 'list_models' which lists all models, but does not explicitly contrast them.

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?

No explicit guidance on when to use this tool versus alternatives. The purpose implies it is for inspecting a single model, but there is no mention of when not to use it or any preconditions.

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