Skip to main content
Glama

get_config

Retrieve current configuration details for the Draw Things app, including active model and settings, to manage image generation workflows.

Instructions

Get the current Draw Things configuration including the loaded model and settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:47-55 (registration)
    Registers the "get_config" MCP tool with the server, providing description, schema, and a handler that calls getConfig(client) and wraps the result.
    server.tool(
      "get_config",
      getConfigDescription,
      getConfigSchema.shape,
      async () => {
        const result = await getConfig(client);
        return { content: result };
      }
    );
  • Defines the Zod input schema (empty object since no params) and description for the get_config tool.
    export const getConfigSchema = z.object({});
    
    export const getConfigDescription =
      "Get the current Draw Things configuration including the loaded model and settings";
  • Core handler logic: fetches configuration from DrawThingsClient, stringifies to JSON text response or error message.
    export async function getConfig(
      client: DrawThingsClient
    ): Promise<{ type: "text"; text: string }[]> {
      try {
        const config = await client.getConfig();
    
        return [
          {
            type: "text",
            text: JSON.stringify(config, null, 2),
          },
        ];
      } catch (error) {
        const message = error instanceof Error ? error.message : String(error);
        return [
          {
            type: "text",
            text: `Error getting config: ${message}. Make sure Draw Things is running with the API Server enabled.`,
          },
        ];
      }
    }
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 what the tool does, not how it behaves. It lacks details on permissions needed, rate limits, error handling, or what 'Get' entails (e.g., is it a read-only operation, does it cache data?). This is a significant gap 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 that front-loads the purpose without waste. Every word contributes to clarifying the tool's function, making it appropriately sized and well-structured for its simplicity.

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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate by stating what configuration is retrieved. However, it lacks details on return values (e.g., format of configuration data) and behavioral context, which could hinder an agent's ability to use it effectively without trial and error.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for not introducing unnecessary information.

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 'Get' and the resource 'current Draw Things configuration', specifying it includes 'loaded model and settings'. This is specific and unambiguous, though it doesn't explicitly differentiate from sibling tools like 'check_status' which might overlap in checking system state.

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 like 'check_status' or other siblings. The description implies usage for retrieving configuration details but doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer based on tool names alone.

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/james-see/mcp-drawthings'

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