Skip to main content
Glama

new_project

Create an empty project in a separate tab, define its width and height, and switch to it to start pixel art editing.

Instructions

Create a new, empty project in a new tab and switch to it.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "new_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 does disclose one real side effect (a new tab is created and focus switches to it), but says nothing about whether the project is persisted, whether save_project is required before closing, whether an unsaved current project is lost, or what is returned.

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?

A single sixteen-word sentence, front-loaded with the action and ending with the resulting state. No filler, no redundancy.

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 simple three-parameter creation tool with no output schema and no annotations, the description covers the core action but leaves the params unexplained and omits persistence/return context. It is thin but not dangerously so.

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?

Schema description coverage is 0%, so the description must compensate and does not. It never mentions 'name', 'width' or 'height', nor units (pixels), defaults, or what happens when width/height are omitted or exceed the 1-4096 bounds documented only in the 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 gives a specific verb and resource ("Create a new, empty project") plus the resulting UI state ("in a new tab and switch to it"). That is enough to distinguish it from get_project, open_file and save_project, though it never names or explicitly contrasts with those siblings.

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?

Usage is only implied: "new, empty" hints that this is for starting fresh rather than loading existing work via open_file. There is no explicit when-to-use, no prerequisites, and no statement about what happens to the currently active project.

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