Skip to main content
Glama
pietermyb

mcp-pdf-reader

close-pdf

Close an open PDF file to free system resources and manage document sessions. Use this tool when finished reading or processing a PDF to maintain optimal performance.

Instructions

Close an open PDF file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_idYesID of the PDF to close

Implementation Reference

  • Handler function for the 'close-pdf' tool. It closes the PDF by removing it from the pdfs and pdf_paths dictionaries, notifies clients of resource changes, and returns a confirmation message.
    elif name == "close-pdf":
        pdf_id = arguments.get("pdf_id")
        if not pdf_id or pdf_id not in pdfs:
            raise ValueError("Invalid PDF ID")
    
        path = pdf_paths[pdf_id]
    
        # Remove from storage
        del pdfs[pdf_id]
        del pdf_paths[pdf_id]
    
        # Notify clients that resources have changed
        await server.request_context.session.send_resource_list_changed()
    
        return [
            types.TextContent(
                type="text",
                text=f"Closed PDF '{os.path.basename(path)}'",
            )
        ]
  • Registration of the 'close-pdf' tool in the list_tools handler, including name, description, and input schema requiring 'pdf_id'.
    types.Tool(
        name="close-pdf",
        description="Close an open PDF file",
        inputSchema={
            "type": "object",
            "properties": {
                "pdf_id": {"type": "string", "description": "ID of the PDF to close"},
            },
            "required": ["pdf_id"],
        },
    ),
  • Input schema definition for the 'close-pdf' tool, specifying the required 'pdf_id' parameter.
    types.Tool(
        name="close-pdf",
        description="Close an open PDF file",
        inputSchema={
            "type": "object",
            "properties": {
                "pdf_id": {"type": "string", "description": "ID of the PDF to close"},
            },
            "required": ["pdf_id"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether closing frees resources, requires specific permissions, affects other operations, or has side effects (e.g., unsaved changes lost). The description is minimal and lacks context beyond the core function.

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 a single, efficient sentence with zero waste. It's appropriately sized for a simple tool and front-loaded with the core action, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a mutation tool. It doesn't explain what happens after closing (e.g., success confirmation, error handling, or resource implications), leaving gaps in understanding the tool's full behavior and outcomes.

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%, with the single parameter 'pdf_id' documented as 'ID of the PDF to close'. The description adds no additional meaning beyond what the schema provides, such as format examples or source of the ID. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('close') and target resource ('an open PDF file'), providing specific verb+resource pairing. However, it doesn't differentiate from sibling tools like 'open-pdf' or 'pdf-to-text' beyond the obvious inverse relationship, missing explicit sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., PDF must be open), exclusions, or relationships with sibling tools like 'open-pdf' for reopening or 'pdf-to-text' for conversion before closing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pietermyb/mcp-pdf-reader'

If you have feedback or need assistance with the MCP directory API, please join our Discord server