Skip to main content
Glama
duke0317

Image Processing MCP Server

by duke0317

apply_find_edges

Detect edges in images to highlight boundaries and contours for analysis or enhancement using edge detection filters.

Instructions

应用边缘检测滤镜

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler function that validates input, loads image using ImageProcessor, applies PIL's ImageFilter.FIND_EDGES, generates output image data, and returns JSON response.
    async def apply_find_edges(image_data: str) -> list[TextContent]:
        """
        应用边缘检测滤镜
        
        Args:
            image_data: 图片数据(base64编码)
            
        Returns:
            应用滤镜后的图片数据
        """
        try:
            # 验证参数
            if not image_data:
                raise ValidationError("图片数据不能为空")
            
            # 加载图片
            image = processor.load_image(image_data)
            
            # 应用边缘检测滤镜
            edges_image = image.filter(ImageFilter.FIND_EDGES)
            
            # 输出处理后的图片
            output_info = processor.output_image(edges_image, "find_edges")
            
            result = {
                "success": True,
                "message": "边缘检测滤镜应用成功",
                "data": {
                    **output_info,
                    "filter_type": "find_edges",
                    "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:312-325 (registration)
    MCP tool registration using FastMCP's @mcp.tool() decorator. Provides input schema via Pydantic Annotated Field and delegates execution to the core handler in filters.py.
    @mcp.tool()
    def apply_find_edges(
        image_source: Annotated[str, Field(description="图片源,可以是文件路径或base64编码的图片数据")]
    ) -> str:
        """应用边缘检测滤镜"""
        try:
            result = safe_run_async(filters_apply_find_edges(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 in get_filter_tools() function, though not directly used in main MCP registration.
    Tool(
        name="apply_find_edges",
        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. It mentions applying a filter but doesn't disclose behavioral traits such as whether it modifies the original image, requires specific image formats, has performance implications, or what the output looks like. This is a significant gap for a tool with no annotation coverage.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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), no annotations, and high schema coverage for its single parameter, the description is minimally adequate. However, as a filter application tool with no behavioral disclosure, it lacks completeness in explaining effects or usage context, scoring at the minimum viable level.

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

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

Purpose3/5

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

The description '应用边缘检测滤镜' (apply edge detection filter) states a clear verb ('apply') and resource ('edge detection filter'), but it's somewhat vague about what 'edge detection' entails and doesn't distinguish from sibling tools like 'apply_contour' or 'apply_edge_enhance'. It's functional but lacks specificity about the algorithmic approach or visual effect.

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 'apply_contour' or 'apply_edge_enhance', nor does it mention prerequisites or exclusions. It's a standalone statement with no contextual usage information.

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