AnimatedWebs

Get an AnimatedWebs style reference

get_style_reference

Read-onlyIdempotent

Returns the full DESIGN.md for one AnimatedWebs website style reference (colour tokens, type scale, radius, buttons, layout notes, build prompt) plus a Tailwind v4 @theme block and CSS variables. Use it after search_catalog (kind styles) to build original work in that style; use get_template for a ready AnimatedWebs template. It is guidance only: do not copy the source site's logo, images, copy or trademarks. No credits, no pagination. Read-only. Unknown slugs return an error. Example: {"slug":"stripe"}.

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": {
      "slug": "<slug>"
    },
    "name": "get_style_reference"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Style slug exactly as returned by search_catalog (kind styles), e.g. 'stripe'.

Output Schema

Name	Required	Description
`css`	Yes	CSS custom properties
`name`	Yes
`note`	Yes
`page`	Yes
`source`	Yes	The measured public website
`designMd`	Yes	Markdown design brief
`tailwind`	Yes	Tailwind v4 @theme block

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / slug / description

Previous value: -"Style slug exactly as returned by search (kind styles), for example 'stripe'."New value: +"Style slug exactly as returned by search_catalog (kind styles), e.g. 'stripe'."

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / slug / description

Previous value: -"Style slug exactly as returned by search_styles, for example 'stripe'."New value: +"Style slug exactly as returned by search (kind styles), for example 'stripe'."

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, but the description adds behavior the annotations cannot: no credits are consumed, there is no pagination, unknown slugs return an error, and the content is guidance-only with an explicit prohibition on copying logos, images, copy or trademarks. Those are exactly the operational and licensing constraints an agent needs before calling.

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 dense paragraph that front-loads the return payload, then usage routing, then constraints — every sentence carries information. The trailing 'Example: {"slug":"stripe"}' duplicates the schema example and is the one element that does not earn its place.

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?

An output schema exists, so return values need not be specified, yet the description still summarizes the payload shape. For a one-parameter, read-only lookup it covers purpose, sequencing, failure mode, cost and licensing — nothing material is missing.

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% and the schema already defines the single 'slug' parameter with an example ('stripe'), so baseline is 3. The description only reinforces exact-match lookup via 'Unknown slugs return an error' and repeats the example, adding no new syntax or format meaning beyond 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?

The description opens with a specific verb and resource ('Returns the full DESIGN.md for one AnimatedWebs website style reference') and enumerates the payload (colour tokens, type scale, radius, buttons, layout notes, build prompt, Tailwind v4 @theme block, CSS variables). It explicitly separates itself from the two nearest siblings, search_catalog and get_template, so an agent can pick it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the prerequisite workflow ('Use it after search_catalog (kind styles)'), states the intent ('build original work in that style'), and routes the alternative case explicitly ('use get_template for a ready AnimatedWebs template'). Both when-to-use and when-to-use-something-else are covered.

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

All AnimatedWebs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.