Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Get brand kit

get_brand_kit
Read-onlyIdempotent

Get a workspace's brand kit: brand name and profile; brand voice (purpose, audience, tone, emotions, character, syntax, language); color palettes; logos with asset URLs; and fonts with family, weights, type scale, and specimen links. Use the colors and fonts as inputs to compose_design and the design edit tools.

Inputs: workspace_key; optional brand_kit_id. Without brand_kit_id it returns the workspace's most recent brand kit. Returns a notice if the workspace has no brand kit. Read-only.

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>"
    },
    "name": "get_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_kit_idNoOptional id of a specific brand kit. Defaults to the primary (most recent) kit.
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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral context: without brand_kit_id it returns the most recent kit, and it returns a notice if the workspace has no brand kit. It does not cover permissions or rate limits, but those are not essential here.

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 description is front-loaded with purpose and return contents, then usage, inputs, and fallback behavior. It is efficient and well structured, with only minor redundancy in restating 'Read-only' and the default brand_kit_id behavior already in the schema.

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 no output schema, the description compensates by enumerating the returned fields in detail: brand name/profile, voice components, palettes, logos with URLs, and fonts with weights and specimen links. It also covers the empty-workspace case and default selection, making it complete for invocation.

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 both parameters are already documented in the schema. The description repeats the default-to-most-recent behavior for brand_kit_id, adding only slight value beyond the schema's own description.

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 and resource ('Get a workspace's brand kit') and enumerates exactly what is returned: brand profile, voice, palettes, logos, and fonts. This clearly distinguishes it from sibling tools like search_fonts or compose_design.

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 directs the agent to use the colors and fonts as inputs to compose_design and design edit tools, giving clear downstream usage. It also documents the optional brand_kit_id behavior and the no-kit notice, though it does not state when not to use the tool or name an alternative for retrieving brand assets.

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