Skip to main content
Glama
NightTrek

Ollama MCP Server

by NightTrek

show

Retrieve detailed information about a specific Ollama model to understand its capabilities and configuration before use.

Instructions

Show information for a model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the model

Implementation Reference

  • The main handler function for the 'show' tool. It executes the 'ollama show' CLI command with the model name from arguments and returns the output as text content in the MCP response format. Handles errors by throwing McpError.
    private async handleShow(args: any) {
      try {
        const { stdout, stderr } = await execAsync(`ollama show ${args.name}`);
        return {
          content: [
            {
              type: 'text',
              text: stdout || stderr,
            },
          ],
        };
      } catch (error) {
        throw new McpError(ErrorCode.InternalError, `Failed to show model info: ${formatError(error)}`);
      }
    }
  • Input schema definition for the 'show' tool, requiring a 'name' property of type string.
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Name of the model',
        },
      },
      required: ['name'],
      additionalProperties: false,
    },
  • src/index.ts:95-109 (registration)
    Tool registration in the listTools handler response, defining name, description, and input schema for 'show'.
    {
      name: 'show',
      description: 'Show information for a model',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the model',
          },
        },
        required: ['name'],
        additionalProperties: false,
      },
    },
  • src/index.ts:260-261 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that routes 'show' tool calls to the handleShow method.
    case 'show':
      return await this.handleShow(request.params.arguments);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'show information' which implies a read-only operation, but doesn't disclose behavioral traits such as whether it requires authentication, what happens if the model doesn't exist, rate limits, or the format of returned information. This leaves significant gaps for a tool with no annotation coverage.

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, clear sentence with zero waste: 'Show information for a model.' It's appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary details. Every word earns its place.

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 complexity (simple read operation with 1 parameter), no annotations, and no output schema, the description is incomplete. It doesn't explain what information is shown, potential errors, or return values, leaving the agent with insufficient context to use the tool effectively beyond basic invocation.

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 description coverage is 100% (the 'name' parameter is fully described in the schema), so the baseline is 3. The description doesn't add meaning beyond the schema, as it doesn't elaborate on the 'name' parameter (e.g., format, examples, or constraints). With 1 parameter and high schema coverage, this is adequate but not additive.

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 'Show information for a model' states a general purpose (verb 'show' + resource 'model'), but it's vague about what specific information is shown and doesn't distinguish from siblings like 'list' (which might list models) or 'run' (which might execute a model). It avoids tautology by not restating the tool name 'show' directly.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing model), exclusions, or compare to siblings like 'list' for overviews or 'run' for execution. The description implies usage for viewing details but lacks explicit 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/NightTrek/Ollama-mcp'

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