Skip to main content
Glama
autoexecbatman

Enhanced Architecture MCP

model_list

Discover available local AI models to select the appropriate one for your tasks. This tool helps users identify and choose from installed models.

Instructions

List available local AI models

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'model_list' tool. Fetches the list of available models from the Ollama API at /api/tags, formats them with size and modified time, and returns a formatted text response.
    async getModelList() {
      try {
        const response = await fetch(`${this.ollamaUrl}/api/tags`);
        
        if (!response.ok) {
          throw new Error(`Ollama API error: ${response.status}`);
        }
    
        const data = await response.json();
        const modelList = data.models.map(model => ({
          name: model.name,
          size: this.formatBytes(model.size),
          modified: model.modified_at
        }));
    
        return {
          content: [
            {
              type: 'text',
              text: `Available Local Models:\n\n${JSON.stringify(modelList, null, 2)}`
            }
          ]
        };
      } catch (error) {
        throw new Error(`Failed to get model list: ${error.message}`);
      }
  • Input schema for the 'model_list' tool, which is an empty object since no parameters are required.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
  • Registration of the 'model_list' tool in the ListToolsRequestHandler response, including name, description, and input schema.
    {
      name: 'model_list',
      description: 'List available local AI models',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Dispatch case in CallToolRequestHandler that invokes the getModelList handler for 'model_list' tool calls.
    case 'model_list':
      return await this.getModelList();
  • Helper function used by getModelList to format model file sizes from bytes to human-readable format.
    formatBytes(bytes) {
      if (bytes === 0) return '0 Bytes';
      const k = 1024;
      const sizes = ['Bytes', 'KB', 'MB', 'GB', 'TB'];
      const i = Math.floor(Math.log(bytes) / Math.log(k));
      return parseFloat((bytes / Math.pow(k, i)).toFixed(2)) + ' ' + sizes[i];
    }
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 states 'List available local AI models' which implies a read-only operation, but doesn't specify what 'available' means (e.g., installed, loaded, compatible), whether there are rate limits, authentication needs, or what the output format looks like. This leaves significant behavioral gaps for a tool with zero 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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple listing tool, making it easy to parse quickly.

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 simplicity (0 parameters, no output schema), the description is minimal but adequate for basic understanding. However, with no annotations and no output schema, it fails to address behavioral aspects like what 'available' entails or the return format, leaving the agent with incomplete context for reliable use.

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?

The tool has 0 parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to add parameter semantics, so it meets the baseline expectation for parameterless tools. No additional value is added, but none is required.

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 the verb ('List') and resource ('available local AI models'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'query_local_ai' or 'reasoning_assist' that might also involve local AI models, so it doesn't reach the highest clarity level.

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?

The description provides no guidance on when to use this tool versus alternatives like 'query_local_ai' or 'hybrid_analysis'. It lacks explicit when/when-not instructions or references to sibling tools, leaving usage context implied at best.

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/autoexecbatman/arch-mcp'

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