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 per call, with total and hasMore reported.

Input Schema

TableJSON 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.
`limit`	No	Rows per call (default 400).
`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.

Schema Changelog

Changes observed during successful MCP inspections.

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.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), but the description adds real behavioral context: pagination ceiling (up to 400 rows per call) and the presence of total/hasMore in the response, plus exactly which fields each lean row carries. It does not mention auth requirements or rate limits, hence not 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?

Two sentences, front-loaded with the scope and filtering, then the return shape and routing. The em-dash-heavy second sentence packs a lot in but stays readable; nothing is wasted, though it is dense.

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?

With no output schema, the description carries the burden of describing returns and does so (lean row fields, total and hasMore), and it covers filtering, paging, and alternatives. An agent has everything needed to call this correctly.

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 every parameter including node, rust, type, owner, collection, limit and offset is already documented in the schema. The description restates the filter set and clarifies that rustCrate marks the lead Rust implementation, but adds no syntax or format detail beyond the schema. 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?

States a specific verb and resource ('List components' / registry index) and enumerates the filterable dimensions, which lets an agent distinguish it from mzizi_get_component and mzizi_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?

Explicitly routes to alternatives: 'use get_component for one component in full, or search when you only have words.' Both the alternative and the condition that selects it are named.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?