AnimatedWebs

Open an AnimatedWebs template in a builder

open_builder

Idempotent

Returns links that start a new project from one AnimatedWebs template's build prompt in Lovable, v0 and Bolt; nothing is created until the user opens a link. Use it to hand a template to a hosted AI builder; use get_template with include_prompt true instead to build it yourself in the current project. Same access rule and fair-use cap as get_template with include_prompt: free templates need any signed-in account; a Pro template is included with Pro and Lifetime or spends one Prompt Pack credit on first use (later calls are free). The prompt is embedded in each link, so v0 and Bolt links are left out when longer than 7,000 characters; lovable is always present. Unknown slugs return an error. Example: {"slug":"aurora-site"}.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Template slug exactly as returned by search_catalog (kind templates), e.g. 'aurora-site'.

Output Schema

Name	Required	Description	Default
`links`	Yes
`template`	Yes	Template title

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations are sparse on meaning (readOnlyHint false, openWorld true, idempotent true), and the description explains why: nothing is created until the user opens a link, and a Prompt Pack credit is spent on first use with later calls free. It additionally discloses the 7,000-character truncation rule that omits v0/Bolt links, the guarantee that lovable is always present, and unknown-slug errors — behavior that cannot be inferred from annotations.

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?

The purpose is front-loaded in the first sentence, followed by routing guidance, access rules, and edge cases in a logical order with zero filler. It is dense — the access-rule sentence is long with parentheticals — but every clause carries decision-relevant information.

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?

For a single-parameter tool with an output schema that already documents the returned links, the description covers the remaining gaps an agent needs: cost model, truncation behavior for specific builders, and error handling. Nothing required to call it correctly or set user expectations 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 the baseline is 3; the description goes slightly beyond by giving a concrete invocation example and stating that unknown slugs return an error, which reinforces the need to use exact slugs from search_catalog. It does not add syntax or format detail beyond that.

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 builder links (Lovable, v0, Bolt) for one AnimatedWebs template's build prompt. It immediately distinguishes itself from get_template by naming that sibling and the condition that selects it, so an agent can choose 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?

Gives explicit when-to-use ('hand a template to a hosted AI builder') and when-not ('use get_template with include_prompt true instead to build it yourself in the current project'). It also names prerequisites (signed-in account for free templates, Pro/Lifetime or a Prompt Pack credit for Pro templates) and error conditions.

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.