Skip to main content
Glama
Sign In
pixelblaze

pixelblaze

by tomnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

docs_get_mapper_reference

Retrieve reference documentation for defining spatial coordinates and using render2D/render3D functions with pixel mapping. Use this when working with multi-dimensional LED layouts or spatial effects.

Instructions

Get the PixelBlaze 2D/3D pixel mapping reference documentation.

This covers how to define spatial coordinates for pixels using the mapper, coordinate systems, and the render2D/render3D pattern functions.

Call this when working with multi-dimensional LED layouts or spatial effects.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It describes the tool as retrieving documentation, which implies read-only behavior, but does not explicitly state idempotency, response format, or side effects. The behavior is straightforward, but additional detail would improve transparency.

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, each earning its place: purpose, content summary, usage guidance. Perfectly front-loaded and concise.

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 the tool's simplicity and the existence of an output schema, the description is complete. It covers what the tool does, what content it provides, and when to use it.

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?

There are no parameters, so the schema provides full coverage. Baseline is 4 for zero parameters. The description does not add parameter info, which is appropriate.

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 the tool retrieves PixelBlaze 2D/3D pixel mapping reference documentation. It distinguishes from siblings like docs_get_api_reference and docs_fetch_page by specifying the exact resource and content scope.

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

Usage Guidelines4/5

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

The description provides explicit guidance: 'Call this when working with multi-dimensional LED layouts or spatial effects.' This clearly indicates when to use, though it does not explicitly exclude cases or mention alternatives.

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