Filesystem MCP

server_shutdown

Destructive

Gracefully shuts down the filesystem-mcp server by scheduling an orderly exit after a short delay, allowing in-flight responses to flush before termination.

Instructions

Shut down the filesystem-mcp server process gracefully.

Schedules an orderly exit after a short delay so in-flight responses can flush. Intended for the HTTP daemon; stdio instances exit when the parent closes the stream anyway.

Return Format

{"success": bool, "operation": "shutdown", "result": {"shutdown_in_seconds": int}}

Examples

server_shutdown(confirm=True)

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

Name	Required	Description	Default
`confirm`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0Oct 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Goes beyond the destructiveHint annotation by explaining the mechanism: a short delay so in-flight responses can flush, plus a concrete return payload with shutdown_in_seconds. It does not say whether the process can be restarted by the agent or whether connections are dropped, so it stops short of full disclosure for a destructive operation.

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?

Front-loaded with the core action and mechanism, then structured with clear headings. The Return Format and Examples sections are somewhat redundant given an output schema exists and there is only one trivial parameter, but nothing is bloated.

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?

For a one-parameter destructive tool, the description covers scope, mechanism, and return shape. An agent has enough to call it correctly; only the confirm=false behavior and post-shutdown recovery expectations are unstated.

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 0% and the single `confirm` parameter has no description. The example `server_shutdown(confirm=True)` hints that confirm gates the action, but the description never states what confirm=false (the default) does — presumably a no-op — leaving the most consequential semantic implicit.

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?

Names a specific verb and resource (shut down the filesystem-mcp server process) and scopes it as an orderly exit. This is clearly distinct from siblings like compose_down or file_ops, which act on containers or files rather than the MCP server itself.

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

Usage Guidelines5/5

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

Explicitly states the target context: 'Intended for the HTTP daemon; stdio instances exit when the parent closes the stream anyway.' That tells an agent both when to use it and when it is pointless, which is exactly the routing information needed.

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