Skip to main content
Glama
husniadil

MCP Image Placeholder Server

by husniadil

image_placeholder

Generate placeholder images for testing and development by specifying provider, width, and height parameters.

Instructions

Generate a placeholder image based on a provider, width, and height.
Use this tool to generate a placeholder image for testing or development purposes.

Args:
    provider: The provider to use for the image, must be either `placehold` or `lorem-picsum`.
    width: The width of the image, must be a positive integer between 1 and 10000.
    height: The height of the image, must be a positive integer between 1 and 10000.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYes
widthYes
heightYes

Implementation Reference

  • main.py:8-52 (handler)
    The core handler function for the 'image_placeholder' tool. It validates inputs and generates a URL to a placeholder image from either 'placehold.co' or 'picsum.photos' based on the provider, decorated with @mcp.tool() for registration.
    @mcp.tool()
    def image_placeholder(
        provider: Literal["placehold", "lorem-picsum"],
        width: int,
        height: int,
    ) -> str:
        """
        Generate a placeholder image based on a provider, width, and height.
        Use this tool to generate a placeholder image for testing or development purposes.
    
        Args:
            provider: The provider to use for the image, must be either `placehold` or `lorem-picsum`.
            width: The width of the image, must be a positive integer between 1 and 10000.
            height: The height of the image, must be a positive integer between 1 and 10000.
        """
        # if provider is not in the list of providers, raise a ValueError
        if provider not in ["placehold", "lorem-picsum"]:
            raise ValueError(f"Invalid provider: {provider}")
    
        # if width is not a positive integer between 1 and 10000, raise a ValueError
        if width <= 0 or width > 10000:
            raise ValueError(
                f"Invalid width: {width}. Width must be a positive integer between 1 and 10000"
            )
    
        # if height is not a positive integer between 1 and 10000, raise a ValueError
        if height <= 0 or height > 10000:
            raise ValueError(
                f"Invalid height: {height}. Height must be a positive integer between 1 and 10000"
            )
    
        # if provider is placehold, return the placehold image
        if provider == "placehold":
            return (
                f"https://placehold.co/{width}x{height}"
                if height is not None
                else f"https://placehold.co/{width}"
            )
        # if provider is lorem-picsum, return the lorem-picsum image
        elif provider == "lorem-picsum":
            return (
                f"https://picsum.photos/{width}/{height}"
                if height is not None
                else f"https://picsum.photos/{width}"
            )
  • main.py:9-22 (schema)
    Input schema defined by function parameters and docstring: provider (enum: 'placehold' or 'lorem-picsum'), width/height (positive ints 1-10000), returns string URL.
    def image_placeholder(
        provider: Literal["placehold", "lorem-picsum"],
        width: int,
        height: int,
    ) -> str:
        """
        Generate a placeholder image based on a provider, width, and height.
        Use this tool to generate a placeholder image for testing or development purposes.
    
        Args:
            provider: The provider to use for the image, must be either `placehold` or `lorem-picsum`.
            width: The width of the image, must be a positive integer between 1 and 10000.
            height: The height of the image, must be a positive integer between 1 and 10000.
        """
  • main.py:5-5 (registration)
    Initializes the FastMCP server instance named 'image-placeholder', to which tools are registered.
    mcp = FastMCP("image-placeholder")
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 the tool generates an image but lacks details on behavioral traits like output format (e.g., URL, binary data), error handling, rate limits, or authentication needs. This leaves gaps for an agent to understand how to use it effectively.

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 appropriately sized and front-loaded, with the purpose stated first and parameter details organized in a clear 'Args' section. It avoids unnecessary fluff, though the second sentence slightly repeats the purpose without adding new value.

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 no annotations and no output schema, the description is incomplete for a tool that generates output. It explains parameters well but omits details on what the tool returns (e.g., image URL or data), which is critical for an agent to use it correctly. This gap reduces completeness despite good parameter coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, but the description compensates fully by explaining all three parameters in the 'Args' section: provider options, width/height ranges, and constraints. This adds crucial meaning beyond the bare schema, making parameters clear and actionable.

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

Purpose5/5

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

The description clearly states the specific action ('Generate a placeholder image') and resource ('based on a provider, width, and height'), with the second sentence reinforcing the purpose for testing/development. It uses precise verbs and distinguishes the tool's function without tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool ('for testing or development purposes'), which helps guide the agent. However, since there are no sibling tools mentioned, it cannot differentiate from alternatives, though this is not a flaw given the context.

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/husniadil/mcp-image-placeholder'

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