Skip to main content
Glama
duke0317

Image Processing MCP Server

by duke0317

apply_sharpen

Enhance image clarity and detail by applying a sharpening filter to improve edge definition and visual crispness.

Instructions

应用锐化滤镜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_sourceYes图片源,可以是文件路径或base64编码的图片数据

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core asynchronous handler function that loads the image, applies the SHARPEN filter using PIL, processes the output, and returns JSON-formatted results.
    async def apply_sharpen(image_data: str) -> list[TextContent]:
        """
        应用锐化滤镜
        
        Args:
            image_data: 图片数据(base64编码)
            
        Returns:
            应用滤镜后的图片数据
        """
        try:
            # 验证参数
            if not image_data:
                raise ValidationError("图片数据不能为空")
            
            # 加载图片
            image = processor.load_image(image_data)
            
            # 应用锐化滤镜
            sharpened_image = image.filter(ImageFilter.SHARPEN)
            
            # 输出处理后的图片
            output_info = processor.output_image(sharpened_image, "sharpen")
            
            result = {
                "success": True,
                "message": "锐化滤镜应用成功",
                "data": {
                    **output_info,
                    "filter_type": "sharpen",
                    "size": image.size
                }
            }
            
            return [TextContent(type="text", text=json.dumps(result, ensure_ascii=False))]
            
        except ValidationError as e:
            error_result = {
                "success": False,
                "error": f"参数验证失败: {str(e)}"
            }
            return [TextContent(type="text", text=json.dumps(error_result, ensure_ascii=False))]
            
        except Exception as e:
            error_result = {
                "success": False,
                "error": f"锐化滤镜应用失败: {str(e)}"
            }
            return [TextContent(type="text", text=json.dumps(error_result, ensure_ascii=False))]
  • Tool schema definition including input schema for the apply_sharpen tool, part of get_filter_tools() function.
    Tool(
        name="apply_sharpen",
        description="应用锐化滤镜",
        inputSchema={
            "type": "object",
            "properties": {
                "image_data": {
                    "type": "string",
                    "description": "图片数据(base64编码)"
                }
            },
            "required": ["image_data"]
        }
  • main.py:270-282 (registration)
    MCP server tool registration using @mcp.tool() decorator, which wraps and calls the handler from filters.py via safe_run_async.
    @mcp.tool()
    def apply_sharpen(
        image_source: Annotated[str, Field(description="图片源,可以是文件路径或base64编码的图片数据")]
    ) -> str:
        """应用锐化滤镜"""
        try:
            result = safe_run_async(filters_apply_sharpen(image_source))
            return result[0].text
        except Exception as e:
            return json.dumps({
                "success": False,
                "error": f"应用锐化效果失败: {str(e)}"
            }, ensure_ascii=False, indent=2)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the action without explaining effects (e.g., how much sharpening is applied, whether it's reversible, or if it modifies the original image). It doesn't mention performance implications, output format, or error handling, leaving significant gaps for a mutation tool.

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 extremely concise with a single phrase ('应用锐化滤镜'), front-loading the core action without any wasted words. It efficiently communicates the tool's purpose in minimal space.

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 (which handles return values) and high schema coverage, the description's minimalism is partially excused. However, as a mutation tool with no annotations, it should provide more behavioral context (e.g., effects on the image, typical use cases) to be fully complete for safe agent use.

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?

The schema description coverage is 100%, with the single parameter 'image_source' well-documented in the schema as accepting file paths or base64 data. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for adequate coverage without adding value.

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 '应用锐化滤镜' (apply sharpen filter) clearly states the verb (apply) and resource (sharpen filter), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'adjust_sharpness' or 'apply_edge_enhance', which might have overlapping functionality in image processing contexts.

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 like 'adjust_sharpness' or other image enhancement tools in the sibling list. It lacks any context about specific scenarios, prerequisites, or comparisons with similar 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

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/duke0317/ps-mcp'

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