AnimatedWebs

Request an AnimatedWebs template

request_template

Sends the AnimatedWebs team a request for a new template or component that the catalog does not have, and returns the request id. Use it only after search_catalog found nothing suitable; use manage_request to check, list or cancel requests already sent instead of sending one again. It writes one message to the team's inbox tied to the signed-in account; every call creates a new request, so repeating it makes a duplicate. Requests are reviewed for the weekly template drops and Lifetime members are prioritized. Example: {"request":"a scroll-driven hero for a yacht charter in Miami with a night-sea video"}.

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": {
      "request": "<request>"
    },
    "name": "request_template"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes	What you want built, 10 to 1500 characters: subject, industry, style, references. Example: 'a scroll-driven hero for a yacht charter in Miami with a night-sea video'.

Output Schema

Name	Required	Description
`id`	Yes	Request id for manage_request; null if the inbox did not return one
`status`	Yes
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

changedInput schema / properties / request / description

Previous value: -"What you want built, 10 to 1500 characters: subject, industry, style, references. Example: 'a scroll-driven hero for a yacht charter with a night-sea video'."New value: +"What you want built, 10 to 1500 characters: subject, industry, style, references. Example: 'a scroll-driven hero for a yacht charter in Miami with a night-sea video'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Request id for manage_request; null if the inbox did not return one",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "status": {
+      "const": "received",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "status",
+    "message"
+  ],
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations it discloses that the call writes one message to the team's inbox tied to the signed-in account, that every call creates a duplicate (reinforcing idempotentHint=false with a concrete consequence), that requests feed weekly template drops, and that Lifetime members are prioritized. It also states the return value (request id), though that is partly redundant with the output schema. Minor gap: no mention of rate limits or whether a request can be edited after sending.

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-loaded with the action, then the usage rules, then behavioral consequences, with the search_catalog precondition stated early. The trailing example duplicates the one already embedded in the schema parameter, so it is the one sentence that does not fully 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?

For a single-parameter write tool with full schema coverage and an output schema, nothing an agent needs is missing: it knows the precondition, the duplicate risk, the audience and the return value. Review cadence and prioritization add useful context beyond the minimum.

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 coverage is 100% and the schema parameter already documents the 10–1500 character range, required content (subject, industry, style, references) and the same yacht-charter example, so the description adds little new meaning. The body spelling out what makes a good request is helpful framing but largely restates 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 names a specific verb and resource ("sends the AnimatedWebs team a request for a new template or component") and explicitly scopes it to gaps in the catalog. It also names the two siblings that could be confused with it, search_catalog and manage_request, so an agent can separate the three without opening any 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 gives an explicit precondition ("only after search_catalog found nothing suitable") and a redirect for the alternative case ("use manage_request to check, list or cancel requests already sent instead of sending one again"). Both when-to-use and when-not-to-use are covered with named alternatives.

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.