Skip to main content
Glama

get_project

Retrieve the active Pixelorama project's size, frame count, layers, and current cel to inspect canvas structure before drawing or editing.

Instructions

Describe the project open in Pixelorama: size, frames, layers and the current cel.

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": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full disclosure burden. It does establish that this is a passive inspection operation and identifies the information returned, but it says nothing about behavior in edge cases (no project open), whether it reflects unsaved in-memory state versus on-disk state, or any cost/side-effect profile.

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 front-loaded sentence with no filler. The resource is named first and the returned facets are listed compactly after the colon, so the useful content arrives immediately.

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?

With no parameters and no output schema, the description must carry the return-value burden, and it does by enumerating size, frames, layers, and current cel. What remains unstated — error behavior when no project is open, and whether values reflect unsaved edits — is minor for a simple zero-arg read tool.

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?

The tool takes zero parameters and the input schema is an empty object, so there is no parameter meaning to clarify. Baseline 4 applies; the description correctly implies no arguments are needed by not referencing any.

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+resource ("Describe the project open in Pixelorama") and enumerates the returned facets: size, frames, layers, current cel. An agent can distinguish this read-only inspection tool from siblings like new_project, save_project, or add_layer without opening a schema. It stops short of explicitly naming a sibling alternative, which keeps 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?

Usage is only implied: the sentence describes what information is available, from which an agent can infer 'call this to learn project state before manipulating it.' There is no explicit when-to-use, when-not-to-use, or named alternative for related queries such as reading pixel data (read_pixels).

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