Skip to main content
Glama

kobold_abort

Stop text generation processes in KoboldAI by aborting ongoing operations through the MCP server integration.

Instructions

Abort the currently ongoing generation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiUrlNohttp://localhost:5001

Implementation Reference

  • Handler logic for executing the kobold_abort tool (shared with other POST tools): validates input using AbortSchema, then proxies a POST request to KoboldAI API's /api/extra/abort endpoint.
    if (postEndpoints[name]) {
        const { endpoint, schema } = postEndpoints[name];
        const parsed = schema.safeParse(args);
        if (!parsed.success) {
            throw new Error(`Invalid arguments: ${parsed.error}`);
        }
    
        const result = await makeRequest(`${apiUrl}${endpoint}`, 'POST', requestData);
        return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
            isError: false,
        };
  • Input schema for kobold_abort tool, inheriting from BaseConfigSchema which provides optional apiUrl.
    const AbortSchema = BaseConfigSchema;
  • src/index.ts:338-338 (registration)
    Maps the kobold_abort tool name to its KoboldAI API endpoint and schema for dispatching in the CallTool handler.
    kobold_abort: { endpoint: '/api/extra/abort', schema: AbortSchema },
  • src/index.ts:223-227 (registration)
    Registers kobold_abort tool in the ListTools response with name, description, and input schema.
    {
        name: "kobold_abort",
        description: "Abort the currently ongoing generation",
        inputSchema: zodToJsonSchema(AbortSchema),
    },
  • Utility function to make HTTP requests to the KoboldAI backend, used by the kobold_abort handler.
    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?

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose effects like whether it's destructive, requires specific permissions, or has side effects (e.g., stopping generation mid-process), leaving significant gaps in understanding tool behavior.

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, direct sentence with zero waste, front-loading the key action. It's appropriately sized for a simple tool, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description is minimally adequate but incomplete. It lacks context on what 'generation' refers to or the outcome of aborting, which could be inferred from siblings but isn't explicitly covered.

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, but the tool likely requires no user-provided parameters for its core function. The description doesn't mention parameters, which is acceptable here as the default apiUrl suffices, but it doesn't add semantic value beyond the schema.

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 action ('abort') and target ('currently ongoing generation'), which is specific and unambiguous. However, it doesn't explicitly differentiate from siblings like 'kobold_generate' or 'kobold_complete' that might initiate generations, though the purpose is distinct enough to infer.

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, such as whether it's for interrupting long-running processes or handling errors. It lacks context on prerequisites like needing an active generation, making it minimally helpful for decision-making.

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