Skip to main content
Glama
lihongwen

PDF Reader MCP Server

by lihongwen
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

analyze_pdf_size

Analyze a PDF file to get a detailed size breakdown by content type and receive specific optimization recommendations to reduce file size.

Instructions

Analyze PDF file to identify optimization opportunities.

Provides detailed size breakdown by content type (text, images, metadata, etc.)
and recommends specific optimization strategies for file size reduction.

Args:
    file_path: Path to PDF file to analyze
    
Returns:
    JSON string with size analysis breakdown and optimization recommendations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.6/5.0
Behavior2/5

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

No annotations provided, and the description does not explicitly state that the tool is read-only or disclose any side effects. It focuses on output but omits behavioral traits like file existence requirements or performance implications.

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?

Description is four sentences with front-loaded purpose. No redundant information; each sentence adds value.

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?

Given the single parameter and presence of an output schema, the description adequately explains the tool's input (file path) and output (JSON string with breakdown and recommendations). Minor gap: no mention of error handling for missing files.

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 description adds 'Path to PDF file to analyze' which clarifies the parameter's purpose beyond the schema's string type. However, for a single parameter, the description is minimal and does not specify format or validation.

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?

Description clearly states 'analyze PDF file to identify optimization opportunities' and details the breakdown by content type. It distinguishes from sibling tools like compress_pdf_images and optimize_pdf by focusing on analysis rather than transformation.

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?

Implies usage before optimization but lacks explicit when-to-use or when-not-to-use guidance. No mention of alternatives despite having sibling tools like optimize_pdf.

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/lihongwen/pdfreadermcp'

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