AnimatedWebs

Get an AnimatedWebs UI component

get_component

Read-onlyIdempotent

Returns one AnimatedWebs UI library component by id: description, runtime, interaction, tags, every variant with live URL and thumbnail, import name, shadcn install command, and with include_source true its complete source code (Pro). Use it after search_catalog (kind components) to inspect a component and then add it to a project; use generate_component instead when nothing in the library fits. Details never spend a credit. include_source needs AnimatedWebs Pro (others get an error with the pricing link) and returns code: the renderer and shared files with a per-account watermark, filling about 120,000 characters; files that did not fit have no code and are named in code.omitted, so call again with that path to get one file. New components count toward a fair-use cap (40 per 10 minutes, 150 a day, 500 a week, shared with get_background) that never blocks one already opened today. Unknown ids return an error. Example: {"id":"aurora-hero","include_source":true}.

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": {
      "id": "<id>"
    },
    "name": "get_component"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Component id exactly as returned by search_catalog (kind components), e.g. 'aurora-hero'.
`path`	No	One file path from code.files or code.omitted of an earlier call for the same id; returns only that file in code.files. Implies include_source.
`include_source`	No	true adds code with the source files (Pro only). Default false: public details only.

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`code`	No	Only with include_source or path
`tags`	Yes
`title`	Yes
`source`	Yes	pro: full source available with AnimatedWebs Pro; none: no source bundle
`install`	Yes
`license`	Yes
`runtime`	Yes
`category`	Yes
`variants`	Yes
`thumbnail`	Yes
`importName`	Yes
`description`	Yes
`interaction`	Yes
`shadcnSetup`	Yes
`shadcnInstall`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 8, 2026

changedInput schema / properties / id / description

Previous value: -"Component id, exactly as returned by search (kind components)."New value: +"Component id exactly as returned by search_catalog (kind components), e.g. 'aurora-hero'."

addedInput schema / properties / include_source

Added value: +{
+  "default": false,
+  "description": "true adds code with the source files (Pro only). Default false: public details only.",
+  "type": "boolean"
+}

addedInput schema / properties / path

Added value: +{
+  "description": "One file path from code.files or code.omitted of an earlier call for the same id; returns only that file in code.files. Implies include_source.",
+  "type": "string"
+}

addedOutput schema / properties / code

Added value: +{
+  "additionalProperties": false,
+  "description": "Only with include_source or path",
+  "properties": {
+    "assets": {
+      "description": "Asset list from the source bundle"
+    },
+    "exportName": {
+      "type": "string"
+    },
+    "files": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "bytes": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "code": {
+            "description": "Missing when the file did not fit; fetch it with path",
+            "type": "string"
+          },
+          "language": {
+            "type": "string"
+          },
+          "lines": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "path": {
+            "type": "string"
+          },
+          "shared": {
+            "description": "Shared helper used by several components",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "path",
+          "language",
+          "lines",
+          "bytes",
+          "shared"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "omitted": {
+      "description": "Paths without code in this reply",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "runtime": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "exportName",
+    "runtime",
+    "files",
+    "omitted"
+  ],
+  "type": "object"
+}

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / id / description

Previous value: -"Component id, exactly as returned by search_components or search_everything."New value: +"Component id, exactly as returned by search (kind components)."

First observedNov 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond readOnlyHint/idempotentHint, the description discloses credit cost (details never spend a credit), Pro gating on include_source with a pricing-link error, watermarking, the ~120,000-character payload ceiling with code.omitted fallback, per-account fair-use caps shared with get_background, and error behavior on unknown ids. These are operational constraints the annotations cannot express.

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?

Front-loads what is returned, then routes usage, then constraints, then an example — every sentence carries information. It is a single dense paragraph of roughly 130 words; a short bullet list for the caps and Pro caveats would aid scanning, but there is no filler.

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 no prose explanation, and the description instead covers what the schema cannot: credit cost, rate limits, truncation recovery, and error cases. For a three-parameter read tool with this much operational nuance, nothing an agent needs 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?

Schema coverage is 100%, so baseline is 3, but the description adds real semantics: include_source requires Pro and yields a watermarked renderer plus shared files, and path both implies include_source and is the retry mechanism for files listed in code.omitted. The worked example with a concrete id and flag further anchors usage.

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 specific verb and resource ("Returns one AnimatedWebs UI library component by id") and enumerates the returned payload fields, so an agent knows exactly what it gets back. It distinguishes itself from the sibling generate_component by naming it explicitly.

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?

Gives an explicit ordering: use it after search_catalog (kind components) to inspect a component before adding it to a project. It also states the exclusion condition — use generate_component when nothing in the library fits — leaving nothing to infer.

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.