Skip to main content
Glama

kobold_model_info

Retrieve current model configuration and details from KoboldAI's text generation server for integration and monitoring purposes.

Instructions

Get current model information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiUrlNohttp://localhost:5001

Implementation Reference

  • Handler logic that maps 'kobold_model_info' tool name to the KoboldAI API endpoint '/api/v1/model' and performs a GET request to retrieve the model information.
    const getEndpoints: Record<string, string> = {
        kobold_max_context_length: '/api/v1/config/max_context_length',
        kobold_max_length: '/api/v1/config/max_length',
        kobold_generate_check: '/api/extra/generate/check',
        kobold_model_info: '/api/v1/model',
        kobold_version: '/api/v1/info/version',
        kobold_perf_info: '/api/extra/perf',
        kobold_sd_models: '/sdapi/v1/sd-models',
        kobold_sd_samplers: '/sdapi/v1/samplers',
    };
    
    if (getEndpoints[name]) {
        const result = await makeRequest(`${apiUrl}${getEndpoints[name]}`);
        return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
            isError: false,
        };
    }
  • src/index.ts:183-187 (registration)
    Registration of the 'kobold_model_info' tool in the ListTools response, including its name, description, and input schema derived from ModelInfoSchema.
    {
        name: "kobold_model_info",
        description: "Get current model information",
        inputSchema: zodToJsonSchema(ModelInfoSchema),
    },
  • Definition of the ModelInfoSchema, which is used as the input schema for the kobold_model_info tool and aliases the shared BaseConfigSchema.
    const ModelInfoSchema = BaseConfigSchema;
  • BaseConfigSchema defining the common input structure (apiUrl) used by ModelInfoSchema and many other tools.
    const BaseConfigSchema = z.object({
        apiUrl: z.string().default('http://localhost:5001'),
    });
  • makeRequest utility function that performs HTTP requests to the KoboldAI API, used by the handler for kobold_model_info.
    async function makeRequest(url: string, method = 'GET', body: Record<string, unknown> | null = null) {
        const options: RequestInit = {
            method,
            headers: body ? { 'Content-Type': 'application/json' } : undefined,
        };
        
        if (body && method !== 'GET') {
            options.body = JSON.stringify(body);
        }
    
        const response = await fetch(url, options);
        if (!response.ok) {
            throw new Error(`KoboldAI API error: ${response.statusText}`);
        }
        
        return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get current model information,' implying a read-only operation, but doesn't specify what 'current model' means (e.g., active inference model, default settings), whether it requires authentication, rate limits, or what the output format might be. This is a significant gap 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 'Get current model information' is a single, efficient sentence that front-loads the core action and resource. There's no wasted wording, making it appropriately concise and well-structured for its purpose.

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 complexity (a tool with no annotations, no output schema, and 0% schema description coverage), the description is incomplete. It doesn't explain what 'model information' includes, how it differs from sibling tools, or behavioral aspects like response format. This leaves the agent with insufficient context to use the tool effectively.

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 input schema has one parameter ('apiUrl') with 0% description coverage, and the description doesn't mention parameters at all. However, since there's only one optional parameter (0 required), the baseline is high. The description doesn't add meaning beyond the schema, but the low parameter count minimizes the impact, keeping it from a lower score.

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 'Get current model information' clearly states the verb ('Get') and resource ('current model information'), making the purpose understandable. However, it doesn't differentiate from potential sibling tools that might also retrieve model-related data, such as 'kobold_sd_models' or 'kobold_version', which could provide overlapping or complementary information.

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. With multiple sibling tools like 'kobold_sd_models' (which might list available models) and 'kobold_version' (which could provide version info), there's no indication of whether this tool is for active model status, configuration details, or other specifics, leaving usage ambiguous.

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/PhialsBasement/KoboldCPP-MCP-Server'

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