Skip to main content
Glama
duke0317

Image Processing MCP Server

by duke0317

adjust_contrast

Modify image contrast by adjusting the factor value to enhance or reduce visual clarity and detail visibility in images.

Instructions

调整图片对比度

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_sourceYes图片源,可以是文件路径或base64编码的图片数据
factorYes对比度调整因子,1.0为原始对比度,>1.0增强,<1.0减弱

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler function that loads the image, applies contrast enhancement using PIL ImageEnhance.Contrast, generates output image data, and returns JSON result.
    async def adjust_contrast(image_source: str, factor: float) -> list[TextContent]:
        """
        调整图片对比度
        
        Args:
            image_source: 图片数据(base64编码)或文件路径
            factor: 对比度调整因子(0.0-2.0)
            
        Returns:
            调整后的图片数据
        """
        try:
            # 验证参数
            if not image_source:
                raise ValidationError("图片数据或路径不能为空")
            
            if not validate_numeric_range(factor, 0.0, 2.0):
                raise ValidationError(f"对比度因子必须在0.0-2.0范围内: {factor}")
            
            # 加载图片
            image = processor.load_image(image_source)
            
            # 调整对比度
            enhancer = ImageEnhance.Contrast(image)
            enhanced_image = enhancer.enhance(factor)
            
            # 输出处理后的图片
            output_info = processor.output_image(enhanced_image, "contrast")
            
            result = {
                "success": True,
                "message": f"对比度调整成功: 因子 {factor}",
                "data": {
                    **output_info,
                    "contrast_factor": factor,
                    "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:399-412 (registration)
    MCP tool registration decorator @mcp.tool() that wraps the handler, provides input schema via Annotated Fields, and handles execution with safe_run_async.
    @mcp.tool()
    def adjust_contrast(
        image_source: Annotated[str, Field(description="图片源,可以是文件路径或base64编码的图片数据")],
        factor: Annotated[float, Field(description="对比度调整因子,1.0为原始对比度,>1.0增强,<1.0减弱", gt=0)]
    ) -> str:
        """调整图片对比度"""
        try:
            result = safe_run_async(color_adjust_contrast(image_source, factor))
            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 adjust_contrast tool input, including properties, descriptions, and validation constraints (min/max for factor). Used in get_color_adjust_tools().
    Tool(
        name="adjust_contrast",
        description="调整图片对比度",
        inputSchema={
            "type": "object",
            "properties": {
                "image_source": {
                    "type": "string",
                    "description": "图片数据(base64编码)或文件路径"
                },
                "factor": {
                    "type": "number",
                    "description": "对比度调整因子(0.0-2.0,1.0为原始对比度)",
                    "minimum": 0.0,
                    "maximum": 2.0
                }
            },
            "required": ["image_source", "factor"]
        }
    ),
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. It states the action (adjust contrast) but doesn't cover critical aspects like whether this modifies the original image or creates a new one, performance implications, supported image formats, or error handling. For a mutation tool with zero annotation coverage, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient phrase ('调整图片对比度') that directly conveys the core function without any wasted 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's moderate complexity (image processing with two parameters), no annotations, and the presence of an output schema, the description is minimally adequate. It states what the tool does but lacks behavioral context and usage guidance. The output schema likely covers return values, so the description doesn't need to explain those, but it should address mutation behavior and tool selection.

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 description adds no parameter semantics beyond what the input schema provides. Since schema description coverage is 100%, with clear documentation for 'image_source' and 'factor', the baseline score of 3 is appropriate. The description doesn't compensate but doesn't need to given the comprehensive schema.

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 '调整图片对比度' (adjust image contrast) clearly states the verb (adjust) and resource (image contrast), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like adjust_brightness or adjust_saturation, which follow the same pattern, so it lacks sibling distinction.

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 scenarios where contrast adjustment is preferred over brightness or saturation changes, nor does it reference sibling tools for context. Usage is implied only by the tool name and description.

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