Skip to main content
Glama

ReadImage

Read-only

Reads an image from the shell by providing the file path, making its content accessible for further processing.

Instructions

Read an image from the shell.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes

Implementation Reference

  • Main handler function that reads an image file from disk, base64-encodes it, and returns ImageData with media type.
    def read_image_from_shell(file_path: str, context: Context) -> ImageData:
        # Expand the path before checking if it's absolute
        file_path = expand_user(file_path)
    
        # If not absolute after expansion, join with current working directory
        if not os.path.isabs(file_path):
            file_path = os.path.join(context.bash_state.cwd, file_path)
    
        if not os.path.exists(file_path):
            raise ValueError(f"File {file_path} does not exist")
    
        with open(file_path, "rb") as image_file:
            image_bytes = image_file.read()
            image_b64 = base64.b64encode(image_bytes).decode("utf-8")
            image_type = mimetypes.guess_type(file_path)[0]
            return ImageData(media_type=image_type, data=image_b64)  # type: ignore
  • ImageData model and MEDIA_TYPES literal used by ReadImage handler to represent image output data.
    MEDIA_TYPES = Literal["image/jpeg", "image/png", "image/gif", "image/webp"]
    
    
    class ImageData(BaseModel):
        media_type: MEDIA_TYPES
        data: str
    
        @property
        def dataurl(self) -> str:
            return f"data:{self.media_type};base64," + self.data
  • Registration of ReadImage as an MCP tool with its JSON schema derived from the ReadImage Pydantic model.
    Tool(
        inputSchema=remove_titles_from_schema(ReadImage.model_json_schema()),
        name="ReadImage",
        description="Read an image from the shell.",
        annotations=ToolAnnotations(readOnlyHint=True, openWorldHint=False),
    ),
  • Pydantic schema defining ReadImage input with a single 'file_path' field.
    class ReadImage(BaseModel):
        file_path: str
  • Dispatch logic in get_tool_output that routes ReadImage tool calls to read_image_from_shell.
    elif isinstance(arg, ReadImage):
        context.console.print("Calling read image tool")
        image_data = read_image_from_shell(arg.file_path, context)
        output = image_data, 0.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description adds no extra behavioral context such as what the tool returns (e.g., image format, encoding). It misses the opportunity to complement the annotations.

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 a single, front-loaded sentence with no wasted words. However, its extreme brevity sacrifices informational value for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and parameter descriptions, the definition is incomplete. It does not specify the return value or any constraints, making it insufficient for an agent to use correctly.

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

Parameters2/5

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

With 0% schema description coverage, the description does not compensate. It does not clarify what 'file_path' should be (e.g., absolute vs relative path, supported image formats). The parameter remains vague.

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 'Read an image from the shell' clearly states the tool's action (read) and resource (image), and distinguishes it from siblings like ReadFiles which likely handles text files. However, it does not elaborate on the scope or format.

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?

No guidance is given on when to use this tool versus alternatives such as ReadFiles or FileWriteOrEdit. The description lacks context about scenarios or prerequisites.

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/rusiaaman/wcgw'

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