Skip to main content
Glama
Sign In
invokeai-mcp

invokeai-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

invokeai_shutdown

Gracefully shuts down the InvokeAI MCP server, stopping the connection for AI coding agents. This ensures a clean termination and returns a success or failure message.

Instructions

Gracefully shut down this MCP server.

Return Format

{"success": bool, "message": str}

Examples

invokeai_shutdown()

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

The description indicates a 'graceful' shutdown and specifies the return format, which is useful. However, it does not disclose the destructive consequences (e.g., terminating the server, losing state, irreversibility) or any permissions needed. With no annotations provided, the description carries the full burden and falls short for a shutdown operation.

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 extremely concise and front-loaded. The additional return format and example are directly relevant and help the agent understand the call. No unnecessary information is included.

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

Completeness4/5

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

Given the tool's simplicity (zero parameters, clear purpose, and an output schema), the description provides enough for correct usage. The only gap is the lack of warning about the destructive side effects, but it is otherwise 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. The description adds minimal value beyond the empty schema, but the example invocation 'invokeai_shutdown()' clarifies that no arguments are expected, which is sufficient.

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 action ('Gracefully shut down') and the resource ('this MCP server'). It is specific and distinguishes the tool from siblings like show_invokeai_dashboard_card or invokeai_generate, which are all non-shutdown operations.

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?

The usage is implied by the tool's name and description, but there is no explicit guidance on when to use it or mention of alternatives. The sibling tool invokeai_system could potentially handle system-level operations, but the description does not differentiate or provide exclusions.

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