Skip to main content
Glama

check_status

Verify the Draw Things API server is operational and ready to process image generation requests locally on Mac.

Instructions

Check if the Draw Things API server is running and accessible

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'check_status' tool. It invokes the client's checkStatus method and formats the result as a JSON text block.
    export async function checkStatus(
      client: DrawThingsClient
    ): Promise<{ type: "text"; text: string }[]> {
      const result = await client.checkStatus();
    
      return [
        {
          type: "text",
          text: JSON.stringify(result, null, 2),
        },
      ];
    }
  • Zod schema for the check_status tool input parameters (empty object, no params required).
    export const checkStatusSchema = z.object({});
  • src/index.ts:37-45 (registration)
    Registration of the 'check_status' tool on the MCP server, using the schema, description, and handler function.
    server.tool(
      "check_status",
      checkStatusDescription,
      checkStatusSchema.shape,
      async () => {
        const result = await checkStatus(client);
        return { content: result };
      }
    );
  • Implementation of the DrawThingsClient.checkStatus() method, which checks server status via HTTP fetch to localhost:7860.
    async checkStatus(): Promise<{ running: boolean; message: string }> {
      try {
        const response = await fetch(this.baseUrl);
        if (response.ok) {
          return {
            running: true,
            message: `Draw Things API server is running at ${this.baseUrl}`,
          };
        }
        return {
          running: false,
          message: `Draw Things API server returned status ${response.status}`,
        };
      } catch (error) {
        return {
          running: false,
          message: `Cannot connect to Draw Things API at ${this.baseUrl}. Make sure Draw Things is running and the API Server is enabled in settings.`,
        };
      }
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the tool's purpose (connectivity/health check) but doesn't describe behavioral traits like response format, error conditions, timeout behavior, or authentication requirements. It's minimal but accurate for a simple status check.

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?

Single sentence with zero waste - every word contributes essential information. Front-loaded with the core action ('Check'), followed by the target and purpose. No redundant phrases or unnecessary elaboration.

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 (0 parameters, no annotations, no output schema), the description is complete enough to understand its basic function. However, for a connectivity check tool, additional context about what 'running and accessible' means (e.g., returns status code, response time) would be helpful despite the low complexity.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and doesn't need to compensate for any schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('check if... is running and accessible') and the target resource ('Draw Things API server'), distinguishing it from sibling tools like generate_image or transform_image. It uses precise language that conveys a diagnostic/health-check function rather than data manipulation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (verifying server availability before attempting operations), but doesn't explicitly state when to use this vs. alternatives or provide exclusions. It suggests a prerequisite check but lacks explicit guidance like 'use before calling generate_image if unsure about connectivity'.

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