Skip to main content
Glama
Sign In
pixelblaze

pixelblaze

by tomnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pixelblaze_get_device_info

Retrieves hardware and runtime details from a PixelBlaze controller, including host, pixel count, frames per second, uptime, and firmware version.

Instructions

Get hardware and runtime information about the PixelBlaze device.

Returns a dict with keys: host, pixel_count, fps, uptime_s, version_major, version_minor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/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. It discloses the return structure (dict with specific keys), implying a read-only, safe operation. It could mention it's non-destructive, but given the nature of 'get', it's sufficient.

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?

Two short sentences: one defining the action, the other specifying the return format. No redundant information; every word contributes.

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?

For a zero-parameter, output-schema-present tool, the description is complete. It explains the exact output structure and that no inputs are required. There is no missing context.

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 baseline is 4. The description adds value by listing the return keys, which is especially helpful since no output schema is visible. It clarifies what the tool provides.

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 it retrieves hardware and runtime information of a PixelBlaze device, and lists specific keys. This distinguishes it from sibling tools that manage patterns, brightness, or controls.

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 implicitly conveys usage by stating the tool's purpose. While alternatives are not explicitly mentioned, the sibling tools are all for different tasks, so the context is clear. No exclusions are needed.

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