onenote-mcp

shutdown_server

Gracefully shut down the onenote-mcp server when a user or agent requests to stop the server process. Returns a confirmation string.

Instructions

Shut down the onenote-mcp server gracefully.

Use when the user or an agent explicitly asks to stop the server process.

Return Format

Confirmation string: "✅ Server shutting down...".

Examples

shutdown_server()

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.4Sep 29, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations are empty, so the description carries the full burden. 'Gracefully' hints at a clean shutdown, but it does not disclose whether this is irreversible, what happens to in-flight operations, whether tokens/session state are cleared, or any effect on running indexing jobs — meaningful gaps for a destructive, terminal 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, then cleanly sectioned for usage, return format, and example. The markdown headers are slightly heavy for a zero-parameter tool but nothing is wasted or ambiguous.

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 zero-param tool with an output schema, the definition gives the agent everything needed to select and invoke it. The 'Return Format' block partially duplicates the output schema, but the usage condition and call example round it out adequately.

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 takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate and it correctly shows the no-argument call form in the example.

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 ('shut down') and resource ('the onenote-mcp server'), with the manner ('gracefully') included. It is immediately distinguishable from every sibling (list/export/create/search tools) without opening the schema.

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

Usage Guidelines4/5

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

Explicitly names the trigger condition: when the user or an agent explicitly asks to stop the server process. That is a clear usage context, though no exclusion or alternative is offered (arguably none exists for a single shutdown tool).

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