Skip to main content
Glama
Sign In
pdf-mcp

pdf-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

pdf_shutdown

Destructive

Shut down the pdf-mcp server gracefully, optionally accepting a reason, to stop PDF operations and release resources.

Instructions

Gracefully shut down the pdf-mcp server.

Return Format

A dict with keys:

  • success: bool

  • message: str - shutdown confirmation

Examples

await pdf_shutdown() {"success": true, "message": "Shutting down pdf-mcp."}

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

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional shutdown reason.

Output Schema

NameRequiredDescriptionDefault
messageNoHuman-readable summary
successNoWhether the operation succeeded

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

The destructiveHint=true annotation already flags this as destructive, so the description needn't restate that. It does add value by specifying the shutdown is 'graceful,' implying an orderly stop rather than a hard kill, but it omits what actually gets destroyed (other sessions, in-flight jobs) and whether the action is reversible.

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 front-loaded in a single clear sentence, which is good. However, the Return Format block and the example duplicate what the existing output schema already conveys, so several lines do not earn their 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?

For a low-complexity, zero-required-parameter tool with an output schema present, the description is minimally adequate once return values are excluded. It nonetheless omits the operational impact of shutting down the server, which is the main thing an agent needs before invoking a destructive action.

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 description coverage is 100% and the single optional 'reason' parameter is documented in the schema, so the baseline is 3. The description never mentions the 'reason' parameter and adds no semantics beyond the schema.

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 pdf-mcp server'), clearly distinguishing this from every sibling tool that manipulates or exports PDFs. An agent immediately knows this terminates the server rather than doing document work.

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

Usage Guidelines2/5

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

The description says what the tool does but offers no when-to-use, when-not-to-use, or alternative guidance. It does not warn when shutdown is appropriate, whether other active operations are affected, or how to reverse/restart, leaving usage entirely to inference.

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