Cromanion

cromanion_set_brand

Idempotent

Adjust the palette, fonts and button styling the agent paints its surfaces with. The crawl guesses these from a stylesheet; you probably know the real tokens. Cosmetic only — it changes how the agent looks, never what it may say. Needs the brand permission.

Input Schema

TableJSON Schema

Name	Required	Description
`colors`	No	Hex per role, e.g. {"primary":"#1a1a2e"}. Roles come from cromanion_site_status.
`siteId`	No	Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.
`ctaFill`	No	Primary button background, hex.
`ctaText`	No	Primary button text colour, hex.
`bodyFont`	No	CSS font-family stack for body text, e.g. "Inter, sans-serif".
`ctaRadius`	No	Primary button corner radius, e.g. 8px.
`headingFont`	No	CSS font-family stack for headings, e.g. "Inter, sans-serif".

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`button`	No
`palette`	Yes	The stored colours, by role.
`version`	No	Bumped on every save, so the edge picks the new tokens up.
`typography`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / siteId

Added value: +{
+  "description": "Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.",
+  "type": "string"
+}

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "button": {
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "palette": {
+      "description": "The stored colours, by role.",
+      "type": "object"
+    },
+    "typography": {
+      "type": "object"
+    },
+    "version": {
+      "description": "Bumped on every save, so the edge picks the new tokens up.",
+      "type": [
+        "string",
+        "number"
+      ]
+    }
+  },
+  "required": [
+    "ok",
+    "palette"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 6, 2026

addedInput schema / properties / bodyFont / description

Added value: +"CSS font-family stack for body text, e.g. \"Inter, sans-serif\"."

addedInput schema / properties / headingFont / description

Added value: +"CSS font-family stack for headings, e.g. \"Inter, sans-serif\"."

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses that the operation is cosmetic, that it affects appearance only and not what the agent may say, and that it requires the brand permission. It also explains where current guesses come from ('The crawl guesses these from a stylesheet'), adding useful behavioral context the annotations do not convey.

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 sentences with no filler: purpose is front-loaded, the cosmetic-only boundary is stated early, and the permission requirement is included. Every sentence contributes either to correct tool selection or safe invocation.

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?

For a mutation tool with seven parameters, a nested object, and an output schema, the description supplies the missing non-schema context: why the tool exists, when to use it, its scope boundary, and required permission. The schema covers parameters and the output schema covers return values, so nothing critical is absent.

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 the input schema already documents each parameter. The description adds general context about real tokens versus crawl guesses, but it does not add per-parameter meaning beyond what the schema provides; baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Adjust the palette, fonts and button styling the agent paints its surfaces with.' It also differentiates itself by declaring 'Cosmetic only — it changes how the agent looks, never what it may say,' which clearly separates it from content-affecting siblings like cromanion_set_voice and cromanion_set_playbook.

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 a clear use context: the crawl guesses styling from a stylesheet, so this tool should be used when the agent knows the real tokens. It also provides an explicit exclusion ('never what it may say') and a permission prerequisite, but it does not name specific sibling alternatives to route to for content changes.

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

All Cromanion tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?