Skip to main content
Glama

push_text

Convert text into a formatted image and send it to a Tidbyt or Tronbyt LED sign, with adjustable font size, color, and canvas dimensions.

Instructions

Render text into an image sized for the display (64x32, or 128x64 for wide/2x devices) and push it. Word-wrapped and centered, printable ASCII only. At default sizing: 16 chars/line, 5 lines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoCanvas size. "auto" (default) detects it from the device type (wide/2x devices get 128x64).auto
textYesText to display. \n forces a line break.
colorNoText color as hex, e.g. "#ffcc00". Default white.
device_idNoDevice ID. Omit when the API key can see exactly one device.
text_sizeNo"large" doubles the 4x6 font, "small" is native size. "auto" (default): large on 128x64 (16 chars x 5 lines), small on 64x32. Use small on 128x64 for 32 chars x 10 lines.auto
backgroundNofalse (default): interrupt the display and show this immediately. true: save into the rotation without interrupting.
installation_idNoName for this pushed image (default "text").text
background_colorNoBackground hex color. Default black.
Behavior3/5

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

The description discloses key behaviors: image sizing, word-wrapping, centering, character set, and default line/char limits. Since annotations are absent, it bears full burden but does not clarify overwriting behavior, error conditions, or how background mode affects display queue.

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 uses three short sentences. First sentence states the core action and display sizes, second adds constraints, third gives default metrics. Every sentence carries essential information with no redundancy.

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

Completeness3/5

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

The tool has 8 parameters and no output schema. The description covers core behavior and constraints but lacks details on parameter interactions (e.g., how text_size changes line counts beyond defaults) and does not explain background vs immediate display behavior. Sibling tools are listed but no usage comparison is provided.

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 coverage is 100%, but the description adds value beyond schema by specifying default text size yields 16 chars/line and 5 lines, and mentioning word-wrapping and centering. These details help the agent understand typical output layout not present in the parameter descriptions.

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 renders text into an image sized for the display and pushes it. It specifies display sizes (64x32, 128x64) and default character limits, distinguishing it from siblings like push_image which likely handles arbitrary images.

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 text display with word-wrapping and centering, and restricts to printable ASCII. However, it does not explicitly state when to use this tool versus alternatives like push_image or push_app, nor does it provide exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jonfishr/tronbyt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server