Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Add design shape

add_design_shape

Add a decorative shape, such as a scrim, divider, or badge, to one slide of an existing design. Placement "front" (the default) puts it on top of the content; "back" puts it just above the slide background, behind the content. Existing elements are not changed. 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>",
      "slide": "<slide>",
      "shape": "<shape>"
    },
    "name": "add_design_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeYesThe shape: { "geo": "rectangle"|"roundedRectangle"|"circle"|"pill"|..., "w": <px>, "h": <px>, "x": <px>, "y": <px>, "fill": <color or { "gradient": [<hex>, ...], "angle": <deg> }>, "radius": <px>, "stroke": { "color", "width" }, "rotate": <deg>, "opacity": 0..1, "placement": "front"|"back" }.
slideYesThe slide to add to: "frame" for a single design, or the slide alias ("s1", "s2", ...) from the design structure.
design_idYesThe design id (from compose_design or generate_post) or the key from a /designs/<key> URL.
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

A4.5/5.0
Behavior4/5

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

Annotations already disclose that this is a non-readOnly, non-destructive, non-idempotent mutation. The description adds useful behavioral context beyond that: placement semantics, that existing elements are not changed, that the change is saved, and what the response contains. It could still say more about repeated invocations or permissions, but the key mutation effects are covered.

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 is front-loaded with purpose, then placement semantics, mutation effects, and response contents. Every sentence adds useful information without repetition or filler.

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?

With all parameters fully described in the schema and no output schema present, the description supplies the missing return information: updated design structure with element aliases and positions plus a rendered preview. Combined with annotations and schema, an agent has enough to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description still adds meaningful semantics by explaining that placement defaults to 'front' and what 'front' versus 'back' means in relation to content and background, beyond the schema's enum listing.

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 uses a specific verb and resource: adding a decorative shape to one slide of an existing design. It names concrete examples (scrim, divider, badge) and clearly distinguishes this from sibling tools like add_design_text or add_design_logo.

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?

It clearly states the applicable scenario: adding a decorative shape to one slide of an existing design. It does not explicitly compare this with alternatives such as add_design_text or compose_design, so there are no stated exclusions, but the context is clear enough for correct selection.

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