Skip to main content
Glama

pixel_help

Idempotent

Get a quick-start reference for authoring pixel-art and animation recipes: recipe format, operations, tools, and workflow, plus optional guides, presets, schemas, and examples on request.

Instructions

Start here before drawing pixel art, sprites, tiles, icons, effects or animations. Returns a short quick start: the recipe format, the operations, the tools and the workflow. Pass a topic only when you need more: presets (ready-made fire, smoke, explosions, spells, characters and more to compile instead of drawing, a line each, or with find: "fire" only the ones those words match; full: true adds their animations), preset with name (one preset's source), guide (the full authoring reference and every tool option), workflow (art workflow: poses, scenes, particles, fluids, lighting), craft (short checklists: characters, effects, tiles and scenes, delivery, limits; all three list their sections, and name returns one or what mentions a word), schema (the recipe JSON Schema), example (a complete recipe), or poses, scenes, autotile, fx, fluid, wave, crystal, powder, bodies or normals for those source formats' schemas.

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

Input Schema

NameRequiredDescriptionDefault
findNoWith topic presets: only the presets these words match.
fullNoWith topic presets: each preset's file and animations too.
nameNoWith topic preset: which one; with guide, workflow or craft: a section heading, or a word to find; with a schema: a path such as effects.bodies, or all.
topicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.15.0
    • addedInput schema / properties / find
      Added value: +{
      +  "description": "With topic presets: only the presets these words match.",
      +  "type": "string"
      +}
    • addedInput schema / properties / full
      Added value: +{
      +  "description": "With topic presets: each preset's file and animations too.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"With topic preset: which one; with guide or workflow: a section heading."New value: +"With topic preset: which one; with guide, workflow or craft: a section heading, or a word to find; with a schema: a path such as effects.bodies, or all."
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "guide",
      -  "workflow",
      -  "schema",
      -  "example",
      -  "poses",
      -  "scenes",
      -  "autotile",
      -  "fx",
      -  "fluid",
      -  "wave",
      -  "bodies",
      -  "normals",
      -  "presets",
      -  "preset"
      -]New value: +[
      +  "guide",
      +  "workflow",
      +  "craft",
      +  "schema",
      +  "example",
      +  "poses",
      +  "scenes",
      +  "autotile",
      +  "fx",
      +  "fluid",
      +  "wave",
      +  "crystal",
      +  "powder",
      +  "bodies",
      +  "normals",
      +  "presets",
      +  "preset"
      +]
  2. Changed1 schema field changedv0.12.1
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "guide",
      -  "workflow",
      -  "schema",
      -  "example",
      -  "poses",
      -  "scenes",
      -  "autotile",
      -  "fx",
      -  "fluid",
      -  "wave",
      -  "normals",
      -  "presets",
      -  "preset"
      -]New value: +[
      +  "guide",
      +  "workflow",
      +  "schema",
      +  "example",
      +  "poses",
      +  "scenes",
      +  "autotile",
      +  "fx",
      +  "fluid",
      +  "wave",
      +  "bodies",
      +  "normals",
      +  "presets",
      +  "preset"
      +]
  3. Changed2 schema fields changedv0.11.0
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "With topic preset: which one; with guide or workflow: a section heading.",
      +  "type": "string"
      +}
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "guide",
      -  "workflow",
      -  "schema",
      -  "example",
      -  "poses",
      -  "scenes",
      -  "autotile",
      -  "fx",
      -  "fluid",
      -  "wave",
      -  "normals"
      -]New value: +[
      +  "guide",
      +  "workflow",
      +  "schema",
      +  "example",
      +  "poses",
      +  "scenes",
      +  "autotile",
      +  "fx",
      +  "fluid",
      +  "wave",
      +  "normals",
      +  "presets",
      +  "preset"
      +]
  4. Changed1 schema field changedv0.9.2
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "guide",
      -  "workflow",
      -  "schema",
      -  "example",
      -  "poses",
      -  "scenes",
      -  "autotile",
      -  "fx",
      -  "fluid",
      -  "normals"
      -]New value: +[
      +  "guide",
      +  "workflow",
      +  "schema",
      +  "example",
      +  "poses",
      +  "scenes",
      +  "autotile",
      +  "fx",
      +  "fluid",
      +  "wave",
      +  "normals"
      +]
  5. Changed1 schema field changedv0.9.1
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "poses",
      -  "scenes",
      -  "autotile",
      -  "fx",
      -  "fluid",
      -  "normals"
      -]New value: +[
      +  "guide",
      +  "workflow",
      +  "schema",
      +  "example",
      +  "poses",
      +  "scenes",
      +  "autotile",
      +  "fx",
      +  "fluid",
      +  "normals"
      +]
  6. First observedv0.9.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructive=false, idempotent=true and openWorld=false, and the description adds default-vs-topic behavior and the fact that 'full: true adds their animations'. It does not state that the call has no side effects or describe the shape/size of what comes back, which matters because readOnlyHint is false for a tool that reads documentation. With annotations present the bar is lower, so a 3 is fair.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded, but the second is one enormous run-on sentence with deeply nested parentheticals and inline quotes that is hard to scan. Every clause roughly earns its place, yet the structure works against fast parsing.

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?

There is no output schema, so the description must convey what comes back, and it does at a high level for each topic. For a zero-required-parameter help tool with four optional params, an agent has enough to invoke it correctly; only the source-format schema topics are left under-explained.

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 75%, but the topic enum lists 17 bare values with no per-value documentation; the description compensates by defining what presets, preset, guide, workflow, craft, schema, example and the source-format schemas each return. It also explains the interactions ('find: "fire" only the ones those words match', 'name returns one or what mentions a word'). The final group of source-format schemas ('poses, scenes, autotile... for those source formats' schemas') stays vague, keeping it below a 5.

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 opening sentence gives a specific verb and resource: 'Start here before drawing... Returns a short quick start: the recipe format, the operations, the tools and the workflow.' That makes clear this is the documentation/entry-point tool rather than one of the pixel_compile/pixel_render siblings. It stops short of naming any sibling explicitly, but the 'start here' framing effectively separates it from the action tools.

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

Usage Guidelines5/5

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

It explicitly tells the agent to call it first and to 'Pass a topic only when you need more', which is a clear when-to-use / when-not-to-use split based on progressive disclosure. Each topic value is paired with what it retrieves, so the agent knows which argument to reach for in a given situation.

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