Skip to main content
Glama
Sign In
pixelblaze

pixelblaze

by tomnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pixelblaze_create_pattern

Create and activate a new LED pattern on PixelBlaze by providing JavaScript code that defines a render function.

Instructions

Create a new pattern on the PixelBlaze with the given JavaScript code, then activate it.

Args: name: Display name for the new pattern. code: PixelBlaze JavaScript source code (must define a render(index) function).

Returns a dict with the new pattern's 'id' and 'name'.

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": {
      "name": "<name>",
      "code": "<code>"
    },
    "name": "pixelblaze_create_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so description carries full burden. It discloses that the tool activates the pattern after creation and requires the code to define a render(index) function, providing important behavioral context.

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?

Three sentences plus clear Args block, all concise and front-loaded with the main action. No unnecessary words.

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

Completeness5/5

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

Given two parameters, no annotations, and existing output schema (mentioned in description), this covers purpose, parameter semantics, side effect, and return value completely.

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 description coverage is 0%, so description adds meaning. It explains that 'name' is a display name and 'code' must be PixelBlaze JavaScript with a render(index) function, which goes beyond the schema's title-only fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Create' and resource 'pattern on PixelBlaze', and adds 'then activate it', clearly distinguishing this from sibling tools like pixelblaze_update_pattern or pixelblaze_set_active_pattern.

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 implies when to use this tool by mentioning activation, but does not explicitly state when not to use it or provide alternatives. The purpose is clear but lacks explicit usage boundaries.

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