Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Create colors

create_colors
Destructive

Add colour swatches to a Playbook board — the building blocks of a palette or a brand's colour spec. Send two or more codes and Playbook merges them into a palette (a group asset), returned as group; send one and group comes back null. A colour is a hex code ("#FF0000", "#F00"), CMYK ("CMYK(0%, 100%, 100%, 0%)"), a two-stop gradient ("#FF0000\u2192#0000FF"), or a Pantone name written WITHOUT the "PANTONE " prefix, exactly as it appears in Playbook's Pantone list — "185 C", not "PANTONE 185 C". Anything else is rejected with 406. Returns the finished swatches immediately (nothing is uploaded, so there is no polling step). Requires a token with the write scope. Tip: validate collection_token with get_board first — an unknown token silently falls back to an anonymous default board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titlesNoOptional titles, positionally aligned with color_codes. A null entry falls back to the code itself.
color_codesYes1-100 colours per call. Each is a hex code ("#FF0000", "#F00"), CMYK ("CMYK(0%, 100%, 100%, 0%)"), a two-stop gradient of two hex codes joined by → ("#FF0000\u2192#0000FF"), or a Pantone name with no "PANTONE " prefix and exact casing ("185 C", "185 CP", "20-0001 TPM"). An unrecognized value fails the whole call with 406 — nothing is created.
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.
parent_tokenNoMerge the new swatches into this existing asset or group instead of letting them form a palette of their own.
collection_tokenNoDestination board token. If omitted or unknown, Playbook silently routes to a default anonymous board — call get_board first to validate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "color_codes",
-  "context"
-]New value: +[
+  "color_codes"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: atomic failure semantics ('An unrecognized value fails the whole call with 406 — nothing is created'), no upload or polling step, merge-into-group behavior for multi-code calls, null `group` for single-code calls, and the silent anonymous-board fallback. The description is consistent with destructiveHint=true and idempotentHint=false.

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 purpose is front-loaded and each sentence carries operational weight (formats, error behavior, auth scope, validation tip). It is dense rather than padded, though the colour-format enumeration partially duplicates the schema and makes the paragraph long.

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 five parameters, no output schema, and a mutation with destructive semantics, the description covers return shape (`group` vs null), error behavior, auth scope, and a critical pre-validation step. Nothing an agent needs to invoke it correctly is missing.

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, but the description adds meaning the schema does not: the group/palette merge behavior tied to color_codes cardinality, the exact Pantone prefix convention ('185 C' not 'PANTONE 185 C'), and the rationale for omitting/passing `organization`. It does not fully explain `parent_token` beyond a brief gloss.

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 ('Add colour swatches to a Playbook board') and immediately scopes the concept ('building blocks of a palette or a brand's colour spec'). This clearly separates it from siblings like create_board, create_note, or create_asset_version.

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?

Gives concrete preconditions and routing advice: send one code vs two or more (different return semantics), requires a `write` scope token, and explicitly recommends validating `collection_token` with get_board first because unknown tokens silently fall back to a default board. It lacks an explicit 'do not use this when...' statement, so it stops short of a 5.

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

All Playbook 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