AnimatedWebs

Get an AnimatedWebs creator

get_creator

Read-onlyIdempotent

Returns one verified AnimatedWebs creator's public profile by handle (name, headline, bio, website, stack, specialties, tier, certificate number, profile URL) and their live templates (title, tagline, kind, access, price in USD, stack, demo and preview URLs). Use it after search_catalog (kind creators); for catalog templates use get_template. Never includes prompts. Read-only. Unknown or unverified handles return an error. Example: {"handle":"ada"}.

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": {
      "handle": "<handle>"
    },
    "name": "get_creator"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	Creator handle as returned by search_catalog (kind creators); case-insensitive, no leading slash or @, e.g. 'ada'.

Output Schema

Name	Required	Description	Default
`bio`	Yes
`url`	Yes
`tier`	Yes
`stack`	Yes
`handle`	Yes
`website`	Yes
`headline`	Yes
`templates`	Yes
`specialties`	Yes
`display_name`	Yes
`certificate_no`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / handle / description

Previous value: -"Creator handle as returned by search (kind creators); case-insensitive, without a leading slash."New value: +"Creator handle as returned by search_catalog (kind creators); case-insensitive, no leading slash or @, e.g. 'ada'."

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / handle / description

Previous value: -"Creator handle as returned by search_creators; case-insensitive, without a leading slash."New value: +"Creator handle as returned by search (kind creators); case-insensitive, without a leading slash."

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the safety profile is settled. The description still earns credit by disclosing two things annotations cannot: prompts are never included in the response, and unknown/unverified handles error rather than returning an empty result. It does not discuss rate limits or result caching, which keeps it short of a 5.

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?

Purpose is front-loaded in the first clause, followed by return fields, then routing, then failure behavior — a sensible information order with no filler sentences. The parenthetical field inventories are dense but each item signals what the agent can rely on, though they could be trimmed since an output schema exists.

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 read tool with full schema coverage, annotations, and an output schema, nothing an agent needs is missing: input format, prerequisite call, sibling handoff, error semantics, and content exclusions are all stated. The only redundancy is restating return fields the output schema already defines, which is a style cost rather than a gap.

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 already documents case-insensitivity and the no-leading-slash-or-@ rule, so the description's handle phrasing is largely redundant. It contributes an inline example call ({"handle":"ada"}) and ties the handle back to search_catalog's creator results, which is modest added meaning, so the baseline 3 applies.

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 one verified AnimatedWebs creator's public profile by handle') and enumerates exactly what comes back, including the nested live-templates payload. It explicitly distinguishes itself from get_template and search_catalog, so an agent can route 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 states the sequencing rule ('Use it after search_catalog (kind creators)'), names the alternative for the adjacent need ('for catalog templates use get_template'), and specifies the failure condition for unknown or unverified handles. When-to-use, when-not-to-use, and alternatives are all present.

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.