Skip to main content
Glama

Get brand kit from a website

get_brand_kit
Read-onlyIdempotent

Reads a business's public website and returns its name, a colour palette (with where each colour was found; colours read from the logo are the most reliable, and website-builder default colours are filtered out), logo and icon image URLs, a hero image, a guess at the type of business, and a suggested starting card design built from those. Works without a Leal account. Use the result to propose card designs with preview_card_designs.

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": {
      "url": "<url>"
    },
    "name": "get_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe business's website, e.g. https://beanthere.coffee or beanthere.coffee.
intentNoOptional. One short sentence on what the person asked you to do, e.g. "Set up a stamp card for Ground Up Café". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "description": "Optional. One short sentence on what the person asked you to do, e.g. \"Set up a stamp card for Ground Up Café\". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, but the description adds substantial behavior the agent could not otherwise know: the source is a public website scrape, no account is required, website-builder default colours are filtered out, and logo-derived colours are flagged as most reliable. Those reliability and filtering caveats directly affect how the result should be trusted.

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?

A single dense sentence that leads with the action and then the return payload, followed by one imperative routing sentence. Every clause carries information, though the enumerated return list is long enough that a short structured breakdown would read more easily.

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 no output schema, the description fully carries the burden of describing the return value, and it does so field by field. Combined with the annotation-covered safety profile and the 100%-documented parameters, an agent has everything needed to call it and use the result.

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 both url and intent are already documented in the schema; the description correctly does not duplicate them. It adds a small amount of useful framing by implying the URL is a public business site, which reinforces the format expectation without restating the schema.

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 concrete verb and resource ("Reads a business's public website") and enumerates exactly what comes back: name, colour palette, logo/icon URLs, hero image, business-type guess, and a suggested card design. This is clearly distinguishable from siblings like get_store_setup or list_design_options.

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?

Explicitly routes the agent forward: "Use the result to propose card designs with preview_card_designs." and notes it works without a Leal account, which is a real prerequisite signal. It does not state when NOT to use it (e.g., when a store already has brand data), so it falls short of the 5 bar.

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