Skip to main content
Glama

Complete Brand Colour Intelligence Report

brand_report
Read-only

One-call complete brand colour intelligence report. Input: hex + brand context + markets + medium + product type. Output: archive anchor, cliche contradiction, colour DNA, strategy verdict, commercial signals, market reading per market, usage rules, palette roles, ecommerce copy, memory hooks, Instagram caption, and Midjourney/Flux/DALLE agent brief. One call covers what colour_strategy + cliche_breaker + ecommerce_product_copy + memory_hooks + agent_brief do separately. Two Claude calls total. One complete response.

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": {
      "hex": "<hex>"
    },
    "name": "brand_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexYesHero hex colour e.g. '#4A2A50'
mediumNoMedium e.g. 'packaging', 'digital', 'interior'general
conceptNoOptional concept to search for cliche contradiction e.g. 'luxury', 'eco', 'wellness'
marketsNoTarget markets e.g. ['UK', 'France', 'Japan']
product_typeNoProduct type for copy e.g. 'velvet cushion', 'fragrance', 'cleaning spray'
target_modelNoImage model for agent brief e.g. 'midjourney', 'flux', 'dalle'midjourney
brand_contextNoBrand context: category, positioning, audience, channels

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Structured JSON response. Shape varies by tool; most return an 'ok' boolean plus a 'result' or 'results' field with the tool's data payload.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "error": {
      -      "type": "string"
      -    },
      -    "ok": {
      -      "type": "boolean"
      -    },
      -    "result": {
      -      "type": [
      -        "object",
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With readOnlyHint=true already declaring a safe read, the description still adds useful operating context: 'Two Claude calls total. One complete response.' tells the agent about latency/cost shape and that no follow-up call is required. It says nothing about rate limits, failure modes, or what happens when optional inputs like markets or brand_context are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly, but the thirteen-item output enumeration largely duplicates the output schema and makes the text dense, while 'Two Claude calls total. One complete response.' restates the opening one-call claim. Some trimming would sharpen it without losing information.

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?

Given seven parameters, a nested brand_context object, and an output schema that carries return-value detail, the description supplies enough to call the tool correctly and to know it is a single consolidated call. Only the optional-input behavior and the single-purpose-vs-composite decision are left implicit.

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 every parameter is already documented in the schema, establishing a baseline of 3. The description restates the input list ('hex + brand context + markets + medium + product type') without adding format, default, or interaction semantics beyond what the schema provides.

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?

States a specific deliverable ('complete brand colour intelligence report') and front-loads the one-call framing, then explicitly positions it against the tools it consolidates (colour_strategy, agent_brief, etc.). It is clearly identifiable, though the long output enumeration substitutes for a single crisp verb phrase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The line 'One call covers what colour_strategy + cliche_breaker + ecommerce_product_copy + memory_hooks + agent_brief do separately' implies the agent should prefer this over those individual tools. However it never states the inverse condition (when to use a single-purpose sibling instead, e.g. when only a palette or only an agent brief is needed).

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