Skip to main content
Glama

EarlyLore

earlylore_get_design_dna

Extract computed hero Design DNA and CSS variable specifications from real high-growth products (5-color role HEX & area ratios, heading/body font families, border-radius scale, theme polarity, hero layout structure, and anti-patterns), ready for Tailwind or styles.css.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "earlylore_get_design_dna"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleSlugNoDesign style slug (omit both styleSlug and productSlugOrDomain to list all style overviews)
productSlugOrDomainNoTarget reference product slug or primary domain (e.g. linear.app, postiz.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations give a safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description contributes real value beyond them by spelling out the returned fields and their intended downstream use in Tailwind or styles.css — important since no output schema exists. It omits cost, latency, or auth expectations for an openWorldHint tool, and never clarifies what happens when both slug parameters are supplied.

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 front-loaded sentence with the action verb first, followed by a compact parenthetical inventory of outputs. The enumeration is dense but each item is informative; the trailing "ready for Tailwind or styles.css" earns its place by signaling output format. Slightly heavy for one sentence but no filler.

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 correctly carries the burden of describing return values, and it does so concretely. What is missing for a two-input, open-world read tool is resolution of the ambiguity between the two slugs and any note on combining or omitting them.

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 both parameters are already documented, including the example domains and the list-all behavior. The description adds no meaning beyond the schema — it does not explain the relationship or precedence between styleSlug and productSlugOrDomain when both are provided. 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 ("Extract computed hero Design DNA and CSS variable specifications") and enumerates the concrete artifacts returned: 5-color role HEX with area ratios, font families, border-radius scale, theme polarity, layout structure, anti-patterns. An agent knows exactly what it gets back. It does not, however, distinguish itself from siblings like inspect_product or compare_products, which could plausibly surface overlapping design information.

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 guidance: nothing says when to prefer this over inspect_product, compare_products, or get_niche_benchmark, nor any prerequisite or exclusion. The only scoping hint ("omit both styleSlug and productSlugOrDomain to list all style overviews") duplicates text already present in the schema and describes parameter behavior, not tool selection.

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.