Skip to main content
Glama

Generate Favicon

generate_favicon

Generate a brand-colored SVG monogram favicon from 1–2 letters with readable contrast and ready-to-use HTML embed tags.

Instructions

Create a crisp SVG monogram favicon (1 or 2 letters) on a square, rounded or circle shape in your brand color, with the letter color chosen for readable contrast, plus the HTML tags to use it. Deterministic, no API key needed.

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": {
      "text": "<text>",
      "color": "<color>"
    },
    "name": "generate_favicon"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes1 or 2 characters
colorYesBackground color as hex
shapeNorounded
text_colorNoOptional letter color as hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses determinism, that no API key is required, that letter color is auto-selected for readable contrast, and that the result includes usable HTML tags. What it omits is the return shape (raw SVG string vs. file/URL) and whether any file is written as a side effect.

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?

It is a single front-loaded sentence that moves from the artifact to its options to the accompanying HTML, with no filler. It is clause-dense and slightly run-on, which costs a little readability, but nothing is redundant.

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 4-parameter, non-destructive generator with no output schema and no annotations, the description covers what is produced (SVG plus HTML tags) and key behavior (deterministic, contrast-aware). It stops short of describing the actual response structure or how the SVG is delivered, which is the remaining gap an agent would care about.

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 coverage is 75%, so the baseline is already strong, and the description still adds real meaning: it confirms 'text' is a 1–2 letter monogram, that 'color' is the background/brand color, and that 'text_color' is optional because contrast is chosen automatically. That last point is genuinely new information beyond the schema's 'Optional letter color as hex'.

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 opens with a specific verb and resource: 'Create a crisp SVG monogram favicon (1 or 2 letters)'. It names the shape options, the brand-color input, and the accompanying HTML snippet, so an agent can tell exactly what artifact comes back and that no sibling tool produces it.

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 implied by the artifact name ('favicon') rather than stated as a when-to-use condition, and there are no explicit exclusions or alternatives. Since no sibling generates favicons, the omission is low-risk, but the description never says when this is the right call versus generating a palette or full design system.

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