Skip to main content
Glama
duke0317

Image Processing MCP Server

by duke0317

apply_edge_enhance

Enhance image edges to improve clarity and definition by applying an edge enhancement filter to sharpen visual details.

Instructions

应用边缘增强滤镜

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler function that loads the image, applies PIL's ImageFilter.EDGE_ENHANCE filter, processes output via ImageProcessor, and returns JSON result.
    async def apply_edge_enhance(image_data: str) -> list[TextContent]:
        """
        应用边缘增强滤镜
        
        Args:
            image_data: 图片数据(base64编码)
            
        Returns:
            应用滤镜后的图片数据
        """
        try:
            # 验证参数
            if not image_data:
                raise ValidationError("图片数据不能为空")
            
            # 加载图片
            image = processor.load_image(image_data)
            
            # 应用边缘增强滤镜
            enhanced_image = image.filter(ImageFilter.EDGE_ENHANCE)
            
            # 输出处理后的图片
            output_info = processor.output_image(enhanced_image, "edge_enhance")
            
            result = {
                "success": True,
                "message": "边缘增强滤镜应用成功",
                "data": {
                    **output_info,
                    "filter_type": "edge_enhance",
                    "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))]
  • main.py:284-297 (registration)
    Registers the MCP tool 'apply_edge_enhance' with input schema defined via Annotated[str], wraps the call to filters.py implementation using safe_run_async.
    @mcp.tool()
    def apply_edge_enhance(
        image_source: Annotated[str, Field(description="图片源,可以是文件路径或base64编码的图片数据")]
    ) -> str:
        """应用边缘增强滤镜"""
        try:
            result = safe_run_async(filters_apply_edge_enhance(image_source))
            return result[0].text
        except Exception as e:
            return json.dumps({
                "success": False,
                "error": f"应用边缘增强失败: {str(e)}"
            }, ensure_ascii=False, indent=2)
  • Explicit JSON schema definition for the tool input, requiring 'image_data' as base64 string, part of get_filter_tools().
    Tool(
        name="apply_edge_enhance",
        description="应用边缘增强滤镜",
        inputSchema={
            "type": "object",
            "properties": {
                "image_data": {
                    "type": "string",
                    "description": "图片数据(base64编码)"
                }
            },
            "required": ["image_data"]
        }
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('apply edge enhance filter') but doesn't describe what the tool does beyond that—such as whether it modifies the image in place, returns a new image, has side effects, or requires specific permissions. For a mutation tool with zero annotation coverage, this is a significant gap.

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 that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 that there's an output schema (which likely describes the result), the description doesn't need to explain return values. However, as a mutation tool with no annotations and incomplete behavioral transparency, the description should do more to clarify effects and usage. It's minimally adequate but leaves gaps in understanding the tool's behavior.

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 parameter 'image_source' fully documented in the schema as accepting file paths or base64-encoded image data. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 without compensating for any gaps.

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 verb 'apply' and the resource 'edge enhance filter', making the purpose understandable. It distinguishes this tool from siblings like 'apply_blur' or 'apply_sharpen' by specifying the particular filter type. However, it doesn't explicitly state what edge enhancement does (e.g., accentuates edges in an image), which prevents a perfect score.

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 when edge enhancement is appropriate (e.g., for emphasizing outlines) or when other tools like 'apply_sharpen' or 'apply_contour' might be better. There's no context about prerequisites or exclusions.

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