mzizi-mcp

List components

mzizi_list_components

Read-onlyIdempotent

The registry index, optionally filtered by node, owner, collection, type or rust. Returns a lean row per component (name, type, node, owner, collection, and rustCrate when it has a Mzizi Roots (Rust) implementation, which is the lead) — use get_component for one component in full, or search when you only have words. Paged: up to 400 rows and at most 25000 characters per call; total, has_more and next_offset say how to get the rest.

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

Input Schema

Name	Required	Description
`node`	No	Filter by node number (uncapped).
`rust`	No	true: only components with a Mzizi Roots (Rust) implementation; false: only those without.
`type`	No	Filter by registry type, e.g. registry:ui \| registry:lib \| registry:block.
`astro`	No	true: only components with an Astro implementation (installable with mzizi add --target astro); false: only those without.
`limit`	No	Rows per call (default 400). A page also stops at 25000 characters.
`owner`	No	Filter by owner: mzizi \| nyuchi \| bundu \| framework.
`offset`	No	Rows to skip, for paging.
`collection`	No	Filter by collection, e.g. primitives \| brand \| pages \| resilience.

Output Schema

Name	Required	Description	Default
`hint`	No
`count`	Yes
`items`	Yes
`total`	Yes
`offset`	Yes
`hasMore`	Yes
`has_more`	Yes
`withRust`	Yes
`withAstro`	Yes
`nextOffset`	No
`next_offset`	No
`registryTotal`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 1, 2026

changedInput schema / $schema

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

addedInput schema / properties / collection / maxLength
```
Added value: +100
```

changedInput schema / properties / limit / description

Previous value: -"Rows per call (default 400)."New value: +"Rows per call (default 400). A page also stops at 25000 characters."

addedInput schema / properties / owner / maxLength
```
Added value: +100
```
addedInput schema / properties / type / maxLength
```
Added value: +100
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "hasMore": {
+      "type": "boolean"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "astroFile": {
+            "type": "string"
+          },
+          "name": {},
+          "rustCrate": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextOffset": {
+      "type": "number"
+    },
+    "next_offset": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "registryTotal": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "withAstro": {
+      "type": "number"
+    },
+    "withRust": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "total",
+    "offset",
+    "has_more",
+    "hasMore",
+    "withRust",
+    "withAstro",
+    "items"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / astro

Added value: +{
+  "description": "true: only components with an Astro implementation (installable with mzizi add --target astro); false: only those without.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / rust

Added value: +{
+  "description": "true: only components with a Mzizi Roots (Rust) implementation; false: only those without.",
+  "type": "boolean"
+}

First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real operational context the annotations don't: a per-call page cap of 400 rows and 25000 characters, plus the total/has_more/next_offset paging contract. It does not describe ordering or default sort, which is a modest gap.

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?

Two sentences, front-loaded with purpose then paging facts, no filler. Slightly dense in the middle — the parenthetical about rustCrate being 'the lead' and the full lean-row field list compete with the routing guidance for attention.

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?

An output schema exists, so return values needn't be enumerated, yet the description still summarizes the lean row shape and the paging fields. Combined with the sibling routing, an agent has what it needs; only the omitted astro filter and sort order keep it from being fully complete.

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 description coverage is 100%, so the baseline is 3. The description restates the main filters (node, owner, collection, type, rust) and adds interpretive value on rustCrate ('which is the lead'), but it omits the astro filter entirely and says nothing about limit/offset semantics beyond the paging note.

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?

Names the specific resource (the registry index) and its filterable dimensions, and explicitly differentiates itself from two named siblings (get_component for one full record, search for keyword lookup). An agent can select between list/get/search 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?

Gives explicit routing: use get_component when you need one component in full, use search when you only have words, implying this tool is for enumerating/browsing. The 'optionally filtered by' framing tells the agent filters are optional, matching the zero required parameters.

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

All mzizi-mcp 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.

Resources

Need Help?