Skip to main content
Glama
Sign In
pixelblaze

pixelblaze

by tomnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pixelblaze_get_pattern_code

Retrieve the JavaScript source code for a specific LED pattern by providing its pattern ID.

Instructions

Get the JavaScript source code of a pattern.

Args: pattern_id: The pattern ID to retrieve code for.

Returns the JavaScript source code string.

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": {
      "pattern_id": "<pattern_id>"
    },
    "name": "pixelblaze_get_pattern_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
pattern_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must fully convey behavior. It states it is a read operation returning source code, but does not mention error handling, permissions, or side effects. Adequate for a simple getter.

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?

The description is very concise: a one-line summary followed by an Args section and a return note. Every sentence is essential and front-loaded.

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?

Given the tool has a single parameter and an output schema, the description covers the essentials. It could mention error handling or prerequisites, but overall it is sufficiently complete for such a simple 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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that pattern_id is 'The pattern ID to retrieve code for' and notes the return value is a JavaScript source code string.

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 clearly states 'Get the JavaScript source code of a pattern', using a specific verb and resource. It distinguishes this tool from siblings like pixelblaze_create_pattern or pixelblaze_list_patterns.

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 usage for retrieving pattern source code but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned.

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