Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

open_file

Loads a .pxo project or image file (PNG, JPG, WEBP, BMP, TGA) into a new Pixelorama tab, enabling immediate editing.

Instructions

Open a .pxo project or an image (png, jpg, webp, bmp, tga) in a new tab.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "open_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key side effect (a new tab is created) and the supported formats, but it says nothing about failure modes for unsupported or missing files, whether the new tab becomes active, or whether an already-open file is reused.

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?

One sentence with no filler, and the core action plus the accepted formats and target tab are all front-loaded. Nothing could be removed without losing information.

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?

For a one-parameter tool with no output schema or annotations this covers the essentials, but it leaves open error behavior on unsupported files and what the agent should expect afterward, which matters given there is no structured data to fill those gaps.

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 coverage is 100% and the single 'path' parameter is already documented as 'Path to the file'. The description adds the useful constraint that the path must point to a .pxo or one of the listed image formats, but it does not clarify relative vs. absolute paths or extension handling.

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 names a specific verb (Open) and resource (a .pxo project or image file), enumerates accepted extensions, and states the effect (in a new tab). It does not explicitly contrast with siblings like get_project, get_image, or new_project, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

The accepted file-type list implies when the tool applies (opening a project file or raster image), but there is no explicit when-to-use vs. when-to-use-something-else statement, no mention of prerequisites such as the file existing on disk, and no named alternative for reading pixel data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.