Skip to main content
Glama
Sign In

mzizi-mcp

by io.github.mzizi-dev
OverviewDiscussionsAdmin

Search Mzizi

mzizi_search
Read-onlyIdempotent

Search the registry by words: components, conventions, AI instruction sets and releases. Start here when you do not know the exact name of what you want; use mzizi_get_component once you have a component's name. A component hit with rustCrate has a Mzizi Roots (Rust) implementation, which is the lead; at an equal score it ranks first. Documentation pages are searched by the docs_* tools. Paged: up to 50 hits per call and at most 25000 characters; meta.has_more and meta.next_offset say how to get the rest.

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": {
      "query": "<query>"
    },
    "name": "mzizi_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHits per call (default 50, at most 200).
queryYesFree-text search term, e.g. 'button' or 'date picker'. Every word must match.
offsetNoHits to skip, for paging. Use meta.next_offset from the previous call.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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 / limit
      Added value: +{
+  "description": "Hits per call (default 50, at most 200).",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Hits to skip, for paging. Use meta.next_offset from the previous call.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search term."New value: +"Free-text search term, e.g. 'button' or 'date picker'. Every word must match."
    • addedInput schema / properties / query / maxLength
      Added value: +500
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "additionalProperties": false,
+      "properties": {
+        "data": {
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "astroFile": {
+                "type": "string"
+              },
+              "description": {
+                "type": "string"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "rustCrate": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "name"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "meta": {
+          "additionalProperties": {},
+          "properties": {
+            "count": {
+              "type": "number"
+            },
+            "has_more": {
+              "type": "boolean"
+            },
+            "next_offset": {
+              "type": "number"
+            },
+            "offset": {
+              "type": "number"
+            },
+            "total": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "total",
+            "count",
+            "offset",
+            "has_more"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "data",
+        "meta"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, and the description adds real value beyond them: result-ranking semantics (rustCrate hits rank first at equal score), a character cap, and the meta.has_more / meta.next_offset paging contract. One inaccuracy holds it back — it advertises "up to 50 hits per call" while the schema allows a limit of 200, which could mislead an agent sizing result sets.

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-loaded with purpose and routing guidance before ranking and paging details, and nearly every clause carries operational meaning. Slightly dense — the ranking aside about rustCrate is useful but interrupts the when-to-use flow.

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 need not be described, and pagination plus ranking are covered for a read-only search tool. The only real gap is the 50-vs-200 hit-limit mismatch, which leaves the agent uncertain about the true per-call ceiling.

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 query, limit and offset are already fully documented in the schema; the description adds only paging context (meta.next_offset) and a character ceiling. Baseline 3 applies since the schema does the heavy lifting and the description does not restate parameter formats or syntax.

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 ("Search the registry by words") and enumerates the searchable content types (components, conventions, AI instruction sets, releases). It explicitly separates itself from mzizi_get_component and the docs_* tools, so an agent can route 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 an explicit entry condition ("Start here when you do not know the exact name") plus the hand-off rule ("use mzizi_get_component once you have a component's name"). It also excludes an adjacent domain by naming the docs_* tools as the route for documentation pages.

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
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