Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Add design logo

add_design_logo

Place the workspace's primary brand logo (from its brand kit) on one slide of an existing design. Existing elements are not changed; use move_design_element or set_design_element_width afterwards to adjust it. 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>"
    },
    "name": "add_design_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior4/5

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

Adds real value beyond the annotations: 'Existing elements are not changed' confirms non-destructiveness, 'The change is saved to the design' confirms persistence for a non-read-only tool, and the response contents are described despite no output schema. It doesn't address the non-idempotent hint (e.g., whether calling twice yields duplicate logos) or where on the slide the logo is placed.

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?

Three tight sentences, front-loaded with the action and scope, followed by side-effect, follow-up tools, and return value. No redundancy.

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?

Covers mutation semantics, follow-up operations, and return contents — enough to call it correctly without an output schema. The remaining gap is placement behavior (where the logo lands, whether position is deterministic), which an agent would likely want.

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 description coverage is 100%, so all three parameters are documented in the schema, and the description adds little per-parameter meaning. Notably it never explains placement/positioning behavior, which the 'slide' parameter alone doesn't cover.

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?

Specific verb + resource ('place the workspace's primary brand logo ... on one slide of an existing design'), including where the asset comes from (the brand kit) and the exact scope (one slide of an existing design). This naturally separates it from siblings like add_design_shape and add_design_text, which add different element types.

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?

Explicitly routes follow-up work to move_design_element and set_design_element_width, which tells the agent this tool is placement-only. It states the precondition of an existing design via 'existing design' and 'one slide', but never explicitly says when to prefer it over add_design_shape / add_design_text.

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