Skip to main content
Glama
Sign In
SpriteMCP

SpriteMCP

by NicoRMA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

run_demo

Paints a tiny palette test pattern into the demo subfolder of the output directory, enabling quick color validation for sprite rendering.

Instructions

Paint the tiny palette test pattern under output_dir/demo/.

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

Input Schema

NameRequiredDescriptionDefault
output_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says it will 'paint' a pattern; it does not disclose side effects, whether files are written, whether existing output is overwritten, or what happens when output_dir is null.

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 sentence with no filler. The core action, resource, and destination are front-loaded and compactly expressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

The tool is simple, but with no annotations and no parameter details, the description leaves an agent uncertain about default behavior and side effects. It is too terse to be fully actionable in isolation.

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?

The schema has 0% description coverage on its only parameter, output_dir. The description does hint that output_dir is the base location by saying 'under output_dir/demo/', but it does not explain the null default, path semantics, or relationship to the output root.

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 action ('Paint'), a concrete resource ('tiny palette test pattern'), and a target location ('under output_dir/demo/'). It is clear what the tool does, though it does not explicitly distinguish itself from sibling paint_* tools beyond the 'demo test pattern' framing.

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

Usage Guidelines2/5

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

The description gives no guidance about when to run the demo versus using other tools, nor does it mention any prerequisites or alternatives. The agent must infer that this is a test/demo utility.

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

Deploy Server

Other Tools