StyleKit

List public StyleKit assets

stylekit_list_assets

Read-onlyIdempotent

Browse StyleKit's public asset catalogue by namespace and query. Use the returned kind/id pair with stylekit_get_asset.

Args:

kind (optional): one public namespace such as animation, component-pattern, template, or experience-pack.
query (optional): search public names, descriptions and tags.
offset (number >=0, default 0): results to skip.
limit (number 1-100, default 20): page size.

Returns the full JSON page, including availability, contentLevel, license, attribution, source provenance, and kind counts. An empty page is a successful result. Private user kits and unpublished submissions are not listed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stylekit_list_assets"
  }
}

Input Schema

Name	Required	Description
`kind`	No	Public asset namespace
`limit`	No	Page size
`query`	No	Search names, descriptions and tags
`offset`	No	Results to skip

Output Schema

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`assets`	Yes
`offset`	Yes
`source`	Yes
`hasMore`	Yes
`kindCounts`	Yes
`schemaVersion`	Yes
`fallbackReason`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 7, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / offset / maximum
```
Removed value: -9007199254740991
```

changedOutput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

removedOutput schema / properties / count

Removed value: -{
-  "type": "number"
-}

removedOutput schema / properties / kindCounts / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / next_offset

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "assets",
-  "total",
-  "count",
-  "offset",
-  "limit",
-  "hasMore",
-  "next_offset",
-  "kindCounts",
-  "source"
-]New value: +[
+  "schemaVersion",
+  "assets",
+  "total",
+  "offset",
+  "limit",
+  "hasMore",
+  "kindCounts",
+  "source"
+]

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare this a safe, idempotent, open-world read, so the description is free to add what they cannot: what the payload contains (availability, contentLevel, license, attribution, source provenance, kind counts) and the non-obvious fact that an empty page is a success rather than an error. The exclusion of private and unpublished material is a real behavioral trait an agent could not infer from the schema.

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 purpose sentence, then a scannable Args block, then one sentence on returns and one on exclusions. The Args block duplicates the schema's own descriptions and constraints, so a small amount of space is spent on redundant content, but the structure is clean and nothing is padded.

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 zero-required-parameter listing tool with an output schema, this covers everything an agent needs: pagination defaults, namespace examples, the chained call to stylekit_get_asset, the empty-result case, and the visibility boundary. Nothing material is left to guesswork.

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%, so the Args section largely restates what the schema already declares (defaults, ranges, the query semantics). The marginal value is the concrete namespace examples ('animation, component-pattern, template, experience-pack') against an 18-value enum, which helps an agent pick a value without opening the schema. That is a modest addition on top of an already complete schema, so baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource ('Browse StyleKit's public asset catalogue') plus the two axes of filtering (namespace, query). It also points to the natural follow-up tool, stylekit_get_asset. It stops short of explicitly separating itself from stylekit_search_styles, which is the one sibling an agent could plausibly confuse with the free-text 'query' parameter.

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

Usage Guidelines4/5

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

It gives a clear chained-workflow instruction ('Use the returned kind/id pair with stylekit_get_asset') and states a scope boundary ('Private user kits and unpublished submissions are not listed'). What is missing is an explicit when-to-use-this-instead-of-stylekit_search_styles rule, so the guidance is strong on next steps but silent on the main alternative.

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

All StyleKit 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.