Skip to main content
Glama

Set organization brand kit

set_brand_kit
DestructiveIdempotent

Change the brand kit of an organization. Only the fields you pass change. node_colors are hex colors by shape type, for example {"step":"#1F6FEB"}. guidelines is the naming and tone guide (up to 4000 characters) that the AI uses when it builds organization flows. remove true deletes the brand kit. Upload a logo in the Wavelength app. Only an owner or an admin can do this.

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": {
      "org_id": "<org_id>"
    },
    "name": "set_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoCanvas font: Inter, Arial, Helvetica, Georgia, Roboto, Open Sans, Lato, Montserrat, Source Sans 3, IBM Plex Sans, Poppins, or Nunito Sans. null uses the Wavelength default.
nameNoBrand name.
org_idYesOrganization id from list_organizations.
removeNoDelete the brand kit.
guidelinesNoNaming and tone guide for the AI.
apply_to_aiNo
node_colorsNoHex colors by shape type.
apply_to_canvasNo
logo_on_exportsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds value beyond that with the partial-update semantics ('Only the fields you pass change'), the owner/admin authorization requirement, and the out-of-band logo upload. It does not say whether a removed brand kit is recoverable or what a successful call returns, which matters for a destructive mutation.

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?

Five short sentences, front-loaded with the action and followed by the partial-update rule, parameter clarifications, and the permission constraint in a sensible order. Every sentence carries information; only the logo-upload sentence sits slightly apart from the calling flow.

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?

For a 9-parameter destructive mutation with no output schema, the description covers the essentials an agent needs: partial-update semantics, the delete flag, permissions, and one out-of-scope action. The gaps are the three undocumented apply_to_*/logo_on_exports flags and any statement about success behavior or irreversibility.

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?

At 67% schema coverage the schema carries most parameter meaning, and the description adds genuine detail for two of the nine: a concrete node_colors example ({"step":"#1F6FEB"}) and the 4000-character limit plus AI-consumption context for guidelines. However, apply_to_ai, apply_to_canvas and logo_on_exports have no description in either the schema or the prose, leaving three behavioral flags unexplained.

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 opens with a specific verb and resource ('Change the brand kit of an organization') and immediately clarifies that it is a partial update ('Only the fields you pass change') plus a delete path ('remove true deletes the brand kit'). That distinguishes it clearly from the read-side sibling get_brand_kit without needing to name it, though an explicit pointer to get_brand_kit for reading would have made it a 5.

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 gives real when-to-use context: partial updates are safe, remove=true is the deletion path, and 'Upload a logo in the Wavelength app' tells the agent what this tool cannot do. The prerequisite 'Only an owner or an admin can do this' is also stated. It stops short of naming alternatives for adjacent tasks like reading the kit or changing roles, so it is left at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources