StyleKit

Get a public StyleKit asset

stylekit_get_asset

Read-onlyIdempotent

Retrieve one public asset by its exact kind and id. Source is returned only where the asset's contentLevel and license permit it. Remote templates include their actual file set only when the live source is available; if it is down, the tool returns a structured unavailable error with safe metadata and does not treat a download URL as source code. External and restricted assets expose metadata, license, attribution and source links only.

Args:

kind: the namespace returned by stylekit_list_assets.
id: the exact identifier within that namespace.

Returns complete structured JSON and JSON text, preserving the namespace and provenance.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Exact asset id within the namespace
`kind`	Yes	Public asset namespace

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`source`	Yes
`license`	No
`metadata`	Yes
`sourceUrls`	Yes
`attribution`	No
`capabilities`	Yes
`codeLanguage`	No
`dependencies`	Yes
`schemaVersion`	Yes
`fallbackReason`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 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 / files

Removed value: -{
-  "description": "Exact source file paths to include",
-  "items": {
-    "maxLength": 500,
-    "minLength": 1,
-    "type": "string"
-  },
-  "maxItems": 200,
-  "type": "array"
-}

removedInput schema / properties / includeSource

Removed value: -{
-  "default": true,
-  "description": "Include permitted source files/code; false returns metadata only",
-  "type": "boolean"
-}

changedOutput schema / $schema

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

addedOutput schema / properties / attribution / $ref

Added value: +"#/properties/metadata/properties/attribution"

removedOutput schema / properties / attribution / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / attribution / properties

Removed value: -{
-  "author": {
-    "type": "string"
-  },
-  "license": {
-    "type": "string"
-  },
-  "source": {
-    "type": "string"
-  },
-  "url": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / attribution / required
```
Removed value: -[
-  "source"
-]
```
removedOutput schema / properties / attribution / type
```
Removed value: -"object"
```

addedOutput schema / properties / license / $ref

Added value: +"#/properties/metadata/properties/license"

removedOutput schema / properties / license / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / license / properties

Removed value: -{
-  "name": {
-    "type": "string"
-  },
-  "notes": {
-    "type": "string"
-  },
-  "url": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / license / required
```
Removed value: -[
-  "name"
-]
```
removedOutput schema / properties / license / type
```
Removed value: -"object"
```

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "metadata",
-  "data",
-  "dependencies",
-  "sourceUrls",
-  "capabilities",
-  "source"
-]New value: +[
+  "schemaVersion",
+  "metadata",
+  "dependencies",
+  "sourceUrls",
+  "capabilities",
+  "source"
+]

First observedOct 21, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses real behavioral conditions: source payloads are gated by contentLevel and license, remote templates include file sets only when the live source is reachable, failures surface as a structured unavailable error rather than fabricated source, and external/restricted assets return metadata and links only. That is exactly the extra context annotations cannot carry.

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, followed by conditional return behavior, then a compact Args block. The Args lines largely duplicate the schema descriptions, adding only the list_assets cross-reference, so there is mild redundancy but nothing that obscures the core statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is conditional in a non-obvious way (license gating, live-source dependency, degraded error path) and the description covers all of those, while an output schema handles the return shape. It does not state behavior for an unknown kind/id (as opposed to an unreachable source), which is a small remaining gap.

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 already 100%, so the baseline is 3, but the description adds a genuine semantic link by tying 'kind' to the namespace returned by stylekit_list_assets and stressing the id must be the exact identifier within that namespace. This is more than a restatement of the enum and pattern.

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 opening sentence names a specific verb and resource ('Retrieve one public asset') and constrains it to an exact kind/id pair, which distinguishes it from list_assets and search_styles without naming them. It stops short of explicitly contrasting the sibling tools, so it is clear but not maximally differentiated.

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

Usage Guidelines3/5

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

Usage is only implied through the argument note that 'kind' is 'the namespace returned by stylekit_list_assets', which hints at a list-then-get workflow. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., use search_styles when the id is unknown).

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.