Skip to main content
Glama
Sign In
>sdcraft-mcp

>sdcraft-mcp

by TimkoNZT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

start_server

Starts sd-server to enable local image generation, editing, inpainting, and upscaling; optionally select a profile to control the active configuration.

Instructions

Start sd-server (optionally with the given profile). Lazy autostart also happens on demand.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoProfile name (default: active)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
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 behavioral burden. It does not say whether the call is idempotent when the server is already running, whether it blocks until ready, what errors occur, or what a caller observes on success; only the autostart side-effect is disclosed.

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?

Two short sentences, action first and the autostart caveat second. Nothing is wasted and the essential information is front-loaded.

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?

A simple single-parameter tool with no output schema, so much is not needed. Still, an agent calling a server-start tool needs to know the already-running behavior and whether success is synchronous, and neither is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents the profile parameter with a default of "active". The description merely restates that profile is optional, adding no format or selection semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Start sd-server") plus the optional scoping by profile, which is enough to separate it from stop_server/restart_server. It does not explicitly name a sibling but the action is unambiguous.

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

Usage Guidelines3/5

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

"Lazy autostart also happens on demand" implicitly tells the agent this call is often unnecessary, which is a useful usage hint. However it never says to check server_status first, nor what to do if the server is already running, so the when-to-use guidance stays implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools