Skip to main content
Glama

save_project

Save the active Pixelorama project as a .pxo file to preserve your work; provide a path to choose a new location or omit it to overwrite the last saved file.

Instructions

Save the current project as a .pxo file. Without a path it saves to where it was last saved.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoWhere to save, ending in .pxo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the write target, the .pxo format, and the default-to-last-saved-location fallback, but says nothing about overwrite semantics, whether an existing file is replaced without warning, error conditions, or permission requirements.

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?

Two short sentences with zero filler; the primary action is front-loaded and the default-path behavior follows immediately. 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.

Completeness4/5

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

For a single-optional-parameter save tool with no output schema, the definition covers the essential action and the default-path case. The remaining gap is overwrite/error semantics, which matters for a file-writing tool but is a modest omission at this complexity.

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

Parameters4/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 documented as ending in .pxo, so the baseline would be 3. The description adds genuine meaning by explaining what happens when the parameter is omitted, which the schema does not state.

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?

States a specific verb and resource ('Save the current project') plus the concrete output format (.pxo file), which separates it from siblings like export_png or new_project. It stops short of naming an alternative or clarifying an explicit boundary, so it is clear but not sibling-differentiating in the strongest sense.

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 description explains the conditional behavior when no path is given ('saves to where it was last saved'), which is practical guidance for invocation. However, it offers no when-to-use versus when-not-to-use guidance relative to siblings such as export_png, leaving tool selection implicit.

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