Skip to main content
Glama

Update text, icons or colors

update_elements

Modify GlideDeck canvas elements by ID to update text, icons, colors, fonts, or parallax depth; enable markdown to apply bold, italic, underline, and strikethrough formatting in text boxes.

Instructions

Changes elements by id: text for text boxes (use \n for new paragraphs; with markdown: true, bold, italic, underline and strike become formatting), icon for icons, color (#RRGGBB) for text, icons and shapes, font (a family from list_fonts) for text boxes, parallax for depth in the show (0.3–0.7 far backdrop that drifts slower, negative = near, moves faster).

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": {
      "path": "<path>",
      "updates": "<updates>"
    },
    "name": "update_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe GlideDeck project file (.glide.json). Absolute, or relative to the server's folder; `.glide.json` is added when there is no extension.
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / updates / items / properties / font
      Added value: +{
      +  "description": "Font family for a text box: any font on this computer or added with `add_font` (see `list_fonts`).",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations establish this as a write operation (`readOnlyHint: false`) and not open-world, and "Changes elements" is consistent with that. However, the description does not disclose destructiveness, overwrite behavior, permissions, atomicity, error handling, or what happens when ids are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded with the operation and then lists field-specific rules efficiently. It is somewhat run-on and dense, but every clause carries relevant parameter information.

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?

For a mutation tool with two top-level parameters and no output schema, the definition covers update fields well but leaves important gaps: id acquisition, return/error behavior, and side effects. The annotations cover only write and closed-world status, so the description should do more.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds useful semantics beyond the schema for text, markdown, color format, font source, and parallax depth. It does not explain how to obtain the required `id` values, and with only 50% schema description coverage, the remaining gaps are not fully compensated.

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

Purpose4/5

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

The description states a specific verb and resource: "Changes elements by id," then enumerates the updatable fields. It distinguishes this as an update-by-id operation rather than an add operation, though it does not explicitly name a sibling alternative.

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

Usage Guidelines2/5

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

The only usage cue is "by id," which implies existing elements, plus a reference to `list_fonts` for font values. It does not explain when to use this instead of `add_text` or other siblings, nor does it state prerequisites or exclusions.

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