Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_brand_kit_composite

Build a brand kit from any domain: extract the best-resolution icon, an accessible color palette with text colors, initials avatar and badge assets.

Instructions

[Dynamic Media] Build a brand kit from a domain: best-resolution icon, extracted palette with accessible text colors, initials avatar and badge assets Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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": {
      "domain": "<domain>"
    },
    "name": "caelara_media_brand_kit_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBrand display name (default derived from the domain)
colorNoBrand color override (hex, with or without #)
domainYesBrand domain, e.g. stripe.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; it does contribute real behavioral context — a measured p50/p95 latency and the fact that it calls an external endpoint at media.caelaralabs.com — which implies a network-dependent, generation-style read operation. It omits auth requirements, rate limits, failure behavior, and whether generated assets are returned as URLs or inline markup.

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?

Three compact sentences, front-loaded with the concrete output inventory, and no filler. The benchmark clause with its date and site URL is borderline noise but does serve a latency-budgeting purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a composite generator with no output schema, the description covers what assets are produced and the performance profile, but leaves the return shape unclear (URLs, base64, or SVG strings) and says nothing about auth or side effects of hitting the remote endpoint. Adequate to select the tool, thin for invoking it with confidence.

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 all three parameters are already documented, and this sets the baseline at 3. The description adds only that the kit is built 'from a domain' and that palette text colors are accessibility-checked; the name and color override parameters are not elaborated beyond the schema.

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 names a specific verb and resource ('Build a brand kit from a domain') and enumerates the concrete outputs: best-resolution icon, extracted palette with accessible text colors, initials avatar, and badge assets. That enumeration implicitly distinguishes it from the granular siblings (color_palette_extractor, avatar_initials_svg, badge_shield_generator), but it never explicitly says it bundles their behavior, so an agent must infer the relationship.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative is named. An agent must infer from the word 'composite' and the asset list that this is the bundle-all option rather than a call to the individual sibling generators.

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

Deploy Server

Other Tools