Skip to main content
Glama

Caelara Labs Dynamic Media

brand_kit_composite

Build a brand kit from a domain: best-resolution icon, extracted palette with accessible text colors, initials avatar and badge assets

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": "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 observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it discloses what gets produced (including contrast-aware text colors, which implies computation) but not whether the domain is fetched live, what happens on an unreachable domain, or whether results are deterministic. That leaves meaningful behavioral gaps for a tool with zero annotation coverage.

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?

A single front-loaded sentence with the verb, the input source, and the output list in order of use; no filler or redundancy.

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?

With no output schema, the description steps up by naming the four asset types returned, which is the key thing an agent needs to know. It still omits the return shape (URLs vs. inline SVG vs. structured object), a real gap but a modest one for a read-only asset builder.

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 coverage is 100%, so the domain, name, and color parameters are already fully documented in the schema. The description adds only that the name defaults from the domain and that the palette comes from the domain, which is marginal extra meaning; baseline 3 applies.

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 verb and resource ("Build a brand kit from a domain") and enumerates the deliverables: icon, palette with accessible text colors, initials avatar, badge assets. That distinguishes it from single-purpose siblings like color_palette_extractor or avatar_initials_svg, though it never explicitly says it bundles them.

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?

Usage is only implied: the enumerated outputs signal this is a one-call aggregation of the individual asset generators, so an agent can infer it is the shortcut when all assets are needed. There is no explicit when-to-use/when-not framing or named alternative for single-asset needs.

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