Skip to main content
Glama

read_and_summarize_pdf_file

Extract and condense PDF content into a concise summary by specifying the file path and desired compression ratio. Ideal for quickly accessing key information from lengthy documents.

Instructions

读取PDF文件并总结内容(限制2k字符)

Args:
    filepath: PDF文件路径
    target_ratio: 目标压缩比例,0.1-1.0之间

Returns:
    PDF内容总结

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filepathYes
target_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main execution function for the tool, decorated with @mcp.tool() which also handles registration. Validates input, reads PDF content via helper, summarizes it, and formats the response.
    @mcp.tool()
    async def read_and_summarize_pdf_file(filepath: str, ctx: Context, target_ratio: float = 0.2) -> str:
        """
        读取PDF文件并总结内容(限制2k字符)
        
        Args:
            filepath: PDF文件路径
            target_ratio: 目标压缩比例,0.1-1.0之间
        
        Returns:
            PDF内容总结
        """
        try:
            # 验证参数
            if not 0.1 <= target_ratio <= 1.0:
                return "错误: target_ratio 必须在 0.1 到 1.0 之间"
            
            ctx.info(f"开始读取PDF文件: {filepath}")
            
            # 读取PDF
            content = file_processor.read_pdf_file(filepath)
            
            # 总结内容
            summary = await summarizer.summarize_content(content, target_ratio)
            
            ctx.info("PDF文件读取和总结完成")
            return f"PDF文件: {filepath}\n\n总结:\n{summary}"
            
        except Exception as e:
            logger.error(f"PDF文件总结失败: {e}")
            return f"PDF文件总结失败: {str(e)}"
  • Helper method in FileProcessor class to read and extract text from PDF files using PyPDF2.
    @staticmethod
    def read_pdf_file(filepath: str) -> str:
        """读取PDF文件"""
        try:
            content = ""
            with open(filepath, 'rb') as f:
                pdf_reader = PyPDF2.PdfReader(f)
                
                for page in pdf_reader.pages:
                    content += page.extract_text() + "\n"
            
            return content.strip()
        except Exception as e:
            logger.error(f"读取PDF文件失败 {filepath}: {e}")
            raise Exception(f"无法读取PDF文件: {str(e)}")
  • Core summarization helper in ContentSummarizer class that calls the LLM API to condense content based on target ratio.
        async def summarize_content(self, content: str, target_ratio: float = 0.2, 
                                  custom_prompt: str = None) -> str:
            """
            使用大模型总结内容
            
            Args:
                content: 要总结的内容
                target_ratio: 目标压缩比例 (默认20%)
                custom_prompt: 自定义总结提示词
            
            Returns:
                总结后的内容
            """
            try:
                # 检查内容长度,避免超出限制
                if len(content) > MAX_INPUT_TOKENS * 3:  # 粗略估算token
                    content = content[:MAX_INPUT_TOKENS * 3]
                    logger.warning("内容过长,已截断")
                
                # 构建总结提示词
                if custom_prompt:
                    prompt = custom_prompt
                else:
                    target_length = min(max(int(len(content) * target_ratio), 100), 1000)
    
                    prompt = f"""请将以下内容总结为约{target_length}字的精炼版本,保留核心信息和关键要点:
    
    {content}
    
    总结要求:
    1. 保持原文的主要观点和逻辑结构
    2. 去除冗余和次要信息
    3. 使用简洁明了的语言
    4. 确保信息的准确性和完整性"""
    
                response = self.client.chat.completions.create(
                    model=OPENAI_MODEL,
                    messages=[
                        {"role": "system", "content": "你是一个专业的内容总结专家,擅长将长文本压缩为精炼的摘要。"},
                        {"role": "user", "content": prompt}
                    ],
                    max_tokens=MAX_OUTPUT_TOKENS,
                    temperature=0.1
                )
                
                return response.choices[0].message.content.strip()
                
            except Exception as e:
                logger.error(f"内容总结失败: {e}")
                return f"总结失败: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions a character limit ('限制2k字符') which is useful behavioral context, but doesn't disclose other important traits like error handling, performance characteristics, authentication needs, or rate limits. For a file-reading tool with no annotations, this leaves significant gaps.

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?

The description is efficiently structured with a clear purpose statement, parameter explanations, and return value indication. Every sentence serves a purpose, though the formatting with 'Args:' and 'Returns:' sections could be more integrated into natural language flow.

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?

Given the tool has an output schema (though not shown), the description doesn't need to detail return values. However, for a file-processing tool with no annotations and 2 parameters, it should provide more behavioral context about file access permissions, supported PDF formats, or error conditions. The character limit hint is helpful but insufficient for full completeness.

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?

With 0% schema description coverage, the description must compensate, and it does by explaining both parameters: 'filepath: PDF文件路径' (PDF file path) and 'target_ratio: 目标压缩比例,0.1-1.0之间' (target compression ratio between 0.1-1.0). This adds meaningful context beyond the bare schema, though it doesn't explain how the ratio affects summarization quality or length.

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 tool's purpose: '读取PDF文件并总结内容' (read PDF file and summarize content). It specifies the resource (PDF files) and verb (read and summarize), but doesn't explicitly differentiate from sibling tools like 'read_and_summarize_text_file' or 'summarize_content', which handle similar operations on different inputs.

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. With sibling tools like 'read_and_summarize_text_file', 'summarize_content', and 'summarize_webpage' available, there's no indication of when PDF-specific summarization is preferred over general content summarization tools.

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

Related 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/yzfly/fullscope-mcp-server'

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