Skip to main content
Glama

server_shutdown

Initiates a graceful shutdown of the splatmaker-mcp server so running sessions terminate cleanly. Returns success status with a message confirming the exit.

Instructions

Gracefully shut down this server. Matches the REST /api/shutdown endpoint - both call the same underlying implementation.

Return Format

{"success": True, "status": "shutting_down", "message": str}.

Examples

server_shutdown() -> {"success": True, "status": "shutting_down", "message": "Server will exit in ~0.5s"}

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_shutdown"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations are empty, so the description must carry the full behavioral burden. It does disclose the graceful exit and the ~0.5s termination window plus an exact response shape, but says nothing about what happens to in-flight work, active connections, whether the server can be restarted, or any auth requirement for a destructive teardown.

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

Conciseness3/5

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

The purpose is correctly front-loaded in the first sentence. However, the '## Return Format' block and the '## Examples' block state the same payload twice, and return values are already covered by an output schema, so a notable fraction of the text does not earn its place.

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?

The tool is simple (no parameters, output schema present), so the bar is modest, and the response payload is described well. What is missing is the side-effect profile an agent needs before invoking a teardown: effect on active operations, irreversibility, and any authorization prerequisite, none of which annotations supply.

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?

There are zero parameters, so there is no parameter semantics to add; the baseline for a no-param tool applies. Nothing in the description misleads about inputs, and the schema is closed (additionalProperties: false).

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?

States a specific verb and resource ('Gracefully shut down this server') and adds the identity relationship to the REST /api/shutdown endpoint, which pins down exactly which operation is performed. The sibling names (status/generate tools) are unrelated, so no ambiguity remains.

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 only implied by the name and verb — there is no explicit when-to-use, when-not-to-use, or alternative routing guidance. For a shutdown tool the intent is largely self-evident, but nothing warns the agent to prefer it only when a real teardown is intended rather than a status check.

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