Skip to main content
Glama

mzizi-mcp

by io.github.mzizi-dev
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
nodeNoFilter by node number (uncapped).
rustNotrue: only components with a Mzizi Roots (Rust) implementation; false: only those without.
typeNoFilter by registry type, e.g. registry:ui | registry:lib | registry:block.
astroNotrue: only components with an Astro implementation (installable with mzizi add --target astro); false: only those without.
limitNoRows per call (default 400).
ownerNoFilter by owner: mzizi | nyuchi | bundu | framework.
offsetNoRows to skip, for paging.
collectionNoFilter by collection, e.g. primitives | brand | pages | resilience.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / rust
      Added value: +{
+  "description": "true: only components with a Mzizi Roots (Rust) implementation; false: only those without.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: pagination cap ('up to 400 rows per call'), that total and hasMore are reported, and the exact lean row shape returned. It does not discuss ordering or rate limits, but the added context is substantial.

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-loads the resource, then the alternatives, then the paging contract in a tight two-sentence block with no filler. The em-dash aside on rustCrate is slightly dense but carries real meaning about the lead implementation.

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?

With no output schema, the description takes on the burden of describing return values and does so (name, type, node, owner, collection, rustCrate) plus the paging contract. Adequate for a filtered-list tool; ordering and total semantics are the only minor omissions.

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 every parameter (including astro, limit and offset) is already documented in the schema, and the baseline is 3. The description lists five of the eight filters but adds no format or syntax detail beyond what the schema already provides, so it neither compensates nor regresses.

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 ('The registry index'), names the filter dimensions, and explicitly contrasts itself with get_component (single component) and search (word-based lookup). An agent can distinguish it from all siblings without opening a 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 for one component in full, or search when you only have words' — a when-to-use-this vs. when-to-use-alternative statement with the condition that selects each. Nothing is left to inference.

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

All mzizi-mcp toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources