Skip to main content
Glama
hyzhak

Ollama MCP Server

by hyzhak

Show model info

show

Retrieve detailed information about a specific Ollama model, including its configuration, parameters, and capabilities, to understand and verify model properties before use.

Instructions

Show information for a model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The handler function for the 'show' tool. It takes a model name, calls ollama.show to retrieve model information, formats it as JSON, and returns it. Includes error handling using the formatError helper.
    async ({ name }) => {
      try {
        const result = await ollama.show({ model: name });
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      } catch (error) {
        return { content: [{ type: "text", text: `Error: ${formatError(error)}` }], isError: true };
      }
    }
  • Input schema for the 'show' tool, validating the 'name' parameter as a string using Zod.
    inputSchema: { name: z.string() },
  • src/index.ts:47-62 (registration)
    Registration of the 'show' tool on the MCP server, including the tool name, metadata, input schema, and inline handler function.
    server.registerTool(
      "show",
      {
        title: "Show model info",
        description: "Show information for a model",
        inputSchema: { name: z.string() },
      },
      async ({ name }) => {
        try {
          const result = await ollama.show({ model: name });
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text", text: `Error: ${formatError(error)}` }], isError: true };
        }
      }
    );
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 for behavioral disclosure. It doesn't indicate whether this is a read-only operation, if it requires authentication, what happens on failure, or if there are rate limits. The description only states what the tool does at a surface level without revealing implementation behavior.

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?

The description is extremely concise at just 5 words, which is efficient for such a simple tool. However, this conciseness comes at the cost of being under-specified rather than appropriately detailed. The single sentence is front-loaded but lacks necessary elaboration.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what information is returned, what format it's in, or how to interpret results. Given the sibling tools suggest this is part of a model management system, more context about the tool's role is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage. The description provides no information about the 'name' parameter - what format it accepts, what models are available, or if it's case-sensitive. With low schema coverage, the description fails to compensate by explaining parameter meaning or constraints.

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

Purpose2/5

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

The description 'Show information for a model' restates the tool name 'show' and title 'Show model info' without adding specificity. It uses the verb 'show' which is generic and doesn't distinguish this tool from other 'show'-type operations. No details about what kind of information is shown or what constitutes a 'model' are provided.

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 given about when to use this tool versus alternatives. With sibling tools like 'list', 'create', 'run', and 'chat_completion' available, the description doesn't clarify if this is for metadata, configuration, or status information. There's no mention of prerequisites or when-not-to-use scenarios.

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/hyzhak/ollama-mcp-server'

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