Get a component
mzizi_get_componentFetch one component in full, Rust first. When the component has a Mzizi Roots (Rust) implementation, rust comes first: its crate, the cargo add line, its CONTRACT clause block and the .rs source inline. astro follows when the component has a pure Astro implementation (mzizi-registry#397): its mzizi add --target astro line, the files it installs into src/components/mzizi/ and their dependencies; null otherwise. react follows: the React build (deprioritised; it keeps working, new work goes to Rust), shadcn-shaped with files[] inline, its npx shadcn add line, and vendor: the registry commit, each file's install target, sha256 and a raw URL pinned to that commit, each @/ import with the dependency that installs it, and the live API item URL (labelled live: it can serve a different commit). Each sha256 is of the registry source at path@ref; a file shadcn add writes can differ (it strips "use client" under rsc: false and rewrites aliases). With no Rust, rust is null and lead is "react". Add docs (use cases, variants, a11y: the documented contract) and version history (from the changelog) with include. Former nyuchi-* names resolve to their mzizi-* successors.
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": {
"name": "<name>"
},
"name": "mzizi_get_component"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Component name, e.g. 'button'. | |
| include | No | Extra sections to fetch. Omit for the implementations only. |