Skip to main content
Glama

kobold_perf_info

Retrieve performance metrics from KoboldAI's text generation API to monitor system status and optimize resource usage.

Instructions

Get performance information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiUrlNohttp://localhost:5001

Implementation Reference

  • Maps 'kobold_perf_info' tool calls to the KoboldAI '/api/extra/perf' endpoint and proxies the GET request using makeRequest, returning the JSON response.
    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,
        };
  • Defines the input schema for 'kobold_perf_info' tool as PerfInfoSchema, which aliases BaseConfigSchema (optional 'apiUrl' string for overriding the default KoboldAI API URL).
    const PerfInfoSchema = BaseConfigSchema;
  • src/index.ts:194-197 (registration)
    Registers the 'kobold_perf_info' tool in the ListTools response, providing name, description, and input schema.
        name: "kobold_perf_info",
        description: "Get performance information",
        inputSchema: zodToJsonSchema(PerfInfoSchema),
    },
  • Universal HTTP request helper function used to proxy all tool calls, including 'kobold_perf_info', to the KoboldAI server.
    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 full burden. 'Get performance information' implies a read-only operation, but it doesn't disclose behavioral traits like authentication needs, rate limits, response format, or what 'performance' entails (e.g., system metrics, model speed). This leaves significant gaps for an agent.

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 extremely concise ('Get performance information')—a single phrase with no wasted words. It's front-loaded and appropriately sized for a simple tool, though this brevity contributes to vagueness in other dimensions.

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 no annotations, no output schema, and low parameter coverage, the description is incomplete. For a tool that likely returns performance data, it should specify what information is retrieved, format, or use cases to aid the agent 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?

With 0% schema description coverage and only 1 parameter (apiUrl), the description doesn't add parameter semantics, but the parameter count is low (1). The baseline for 0 parameters is 4, as minimal compensation is needed, though the description doesn't explain the apiUrl's purpose or default value.

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 'Get performance information' states a clear verb ('Get') and resource ('performance information'), but it's vague about what specific performance metrics are retrieved. It doesn't distinguish from siblings like 'kobold_model_info' or 'kobold_version' that might also provide system-related data.

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. With many sibling tools for different operations (e.g., 'kobold_model_info', 'kobold_version'), the description offers no context on use cases, prerequisites, or exclusions.

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