Skip to main content
Glama
Sign In
>sdcraft-mcp

>sdcraft-mcp

by TimkoNZT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

server_status

Retrieve current sd-server state—running status, managed profile/model, port, uptime, and queue—to verify local image-generation readiness.

Instructions

sd-server state: running, managed, profile/model, port, uptime, queue.

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": "server_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure burden. It lists state fields and implies a read operation, but it does not explicitly state that the tool is read-only, has no side effects, or requires no special permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely compact and front-loaded with the resource and state fields. It wastes no words, though the fragmentary style leaves some terms like 'managed' and 'queue' underspecified.

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?

With no output schema, the description is the only source for return-value information. It lists the key state fields but does not explain their types or meanings, particularly 'managed' and 'queue', leaving the definition minimally adequate rather than fully complete.

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 zero parameters, so the baseline is 4. There are no parameter semantics to clarify, and the empty schema is consistent with the description.

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 identifies a specific resource, the sd-server state, and enumerates the state fields returned: running, managed, profile/model, port, uptime, and queue. It clearly distinguishes itself in practice from action-oriented siblings like start_server, stop_server, and restart_server, though it does not explicitly name alternatives.

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?

Usage is implied by the tool name and the state-oriented description, so an agent can infer this is for checking server status. However, the description gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as start_server or restart_server.

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