Skip to main content
Glama

Get a website's brand kit in one call

brand_kit
Read-only

Get a website's brand kit in one call: the site's own logo (URL plus inline SVG when available, not customer logos), favicon, theme color, color palette ranked by usage, brand CSS variables and fonts, read from its HTML and stylesheets. Fast (1-4 s). Price: $0.01 per call (x402, USDC on Base). Without payment, returns the payment requirements.

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": "brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds material behavior: latency (1-4 s), a concrete price ($0.01 per call, x402/USDC on Base), and the exact non-paid outcome ('returns the payment requirements'). It also clarifies extraction semantics ('read from its HTML and stylesheets') and a negative guarantee ('not customer logos'), though it does not discuss failure modes for unreachable or non-HTML URLs.

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?

The scope and payload come first, followed by performance, price, and the unpaid fallback in short, information-dense clauses. There is no filler or repeated schema content.

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?

Even without an output schema, the description effectively defines the return payload field by field, and it covers the payment requirement and speed an agent needs before calling. Nothing essential for a correct first call is missing.

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?

With 100% schema coverage the baseline is 3, but the description contributes pricing context and the two-phase payment protocol (unpaid call returns requirements, then supply the base64 PAYMENT-SIGNATURE) that the schema only summarizes. It stops short of covering error or partial-payment cases.

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 names a specific verb and resource ('Get a website's brand kit') and then enumerates exactly what is returned: site logo (URL plus inline SVG, with the explicit exclusion of customer logos), favicon, theme color, usage-ranked palette, CSS variables and fonts, and the source ('its HTML and stylesheets'). That enumeration lets an agent tell it apart from narrower siblings like favicon or design_tokens without opening any schema.

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?

'in one call' implies it is the aggregated option versus single-signal tools, and the payment flow is spelled out ('Omit on the first call to get the price and requirements'). However, it never explicitly states when to choose this versus a sibling such as favicon or design_tokens, so the routing is only implied.

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.