Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Set design font size

set_design_font_size
DestructiveIdempotent

Set the font size of one text element in an existing design, in points. The text re-wraps in its box. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview.

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": {
      "workspace_key": "<workspace_key>",
      "design_id": "<design_id>",
      "element": "<element>",
      "font_size": "<font_size>"
    },
    "name": "set_design_font_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesThe element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:...").
design_idYesThe design id (from compose_design or generate_post) or the key from a /designs/<key> URL.
font_sizeYesSize in points, e.g. 64.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, idempotent, destructive mutation, so the base burden is lower. The description still adds real value by disclosing that the text re-wraps in its box as a side effect, that the change persists to the design, and that the response includes the updated design structure plus a rendered preview — details absent from the annotations.

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?

Short and front-loaded: the core action and unit come first, followed by side effects and return contents. Structure is slightly choppy with a single-sentence paragraph for the response, but no sentence is wasted.

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?

There is no output schema, and the description compensates by naming what comes back (updated design structure and rendered preview). Combined with the re-wrap side effect and persistence note, an agent has enough to call it correctly; only the absence of guidance on invalid element targets or size limits keeps it short of a 5.

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?

Schema coverage is 100%, so aliases, raw ids, and point units are already documented in the schema; the baseline of 3 applies. The description's only added nuance is 'one text element', which narrows the element parameter to text targets but doesn't enrich the other three parameters.

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?

States a specific verb (set), a specific attribute (font size), and a bounded resource (one text element in an existing design), with the unit of measure (points). This is clearly distinguishable from siblings like set_design_font_weight, set_design_text, and set_design_element_width.

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 phrase 'one text element in an existing design' implies the prerequisite context (a design must already exist, the element must be text), but there is no explicit when-to-use versus alternatives such as set_design_font_weight when adjusting typography, nor any stated precondition about needing a prior compose_design/generate_post call.

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

All Blaze toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources