mzizi-mcp

Get agent skills

mzizi_get_skills

Read-onlyIdempotent

List the published Mzizi agent skills, or fetch one in full. Skills are what an agent loads first. Each skill has a category: dev (how every agent works in every repo: digital-hygiene, progress-report, ship-release, registry-propagation and pr-gates — load these before any dev work), design, language or build. Pass category to get every skill in it in full (e.g. category=dev), or name for one skill. A skill's answer lists the files it ships beside its SKILL.md (scripts such as hygiene.sh, token stylesheets); pass name and file to get one file's content. Each skill is also an MCP resource (mzizi://skills/, files at mzizi://skills//) and a prompt (skill-). Served from the skill files bundled into this server at build time, so they are exactly the text in mzizi-dev/agent-tools at the deployed commit.

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_get_skills"
  }
}

Input Schema

Name	Required	Description
`file`	No	With `name`: a file the skill ships, by the path its `files` list gives (e.g. hygiene.sh). Returns that file's content.
`name`	No	Skill name. Omit to list all.
`category`	No	Return every skill in this category in full: dev (digital-hygiene, progress-report, ship-release, registry-propagation, pr-gates — for every agent in every repo), design, language or build.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / category / description

Previous value: -"Return every skill in this category in full: dev (digital-hygiene, progress-report — for every agent in every repo), design, language or build."New value: +"Return every skill in this category in full: dev (digital-hygiene, progress-report, ship-release, registry-propagation, pr-gates — for every agent in every repo), design, language or build."

Changed3 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 / file

Added value: +{
+  "description": "With `name`: a file the skill ships, by the path its `files` list gives (e.g. hygiene.sh). Returns that file's content.",
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / name / maxLength
```
Added value: +200
```

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Return every skill in this category in full: dev (digital-hygiene, progress-report — for every agent in every repo), design, language or build.",
+  "enum": [
+    "dev",
+    "design",
+    "language",
+    "build"
+  ],
+  "type": "string"
+}

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, closed-world, so the safety bar is low. The description adds genuinely non-derivable behavior: results are served from skill files bundled at build time and match the deployed commit of mzizi-dev/agent-tools, and category lookups return skills 'in full' rather than summaries. It does not discuss size limits or pagination for large categories, which keeps it from 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?

Front-loaded with the core action and then layered by increasing specificity (list → category → name → file), which reads well. It is dense but mostly earns its length; the repeated enumeration of the `dev` category contents and enum values overlaps with what the schema already states.

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 carries the burden of describing returns, and it does so adequately: a skill's answer lists shipped files alongside SKILL.md, and `file` returns that file's content. Provenance is covered too; only edge cases like invalid name/file errors or response size are unaddressed.

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% and the per-property descriptions already define `file`, `name`, and the `category` enum, so the schema does most of the work. The description adds real value on interaction semantics (that `file` only applies together with `name`, and that `category=dev` expands to a named list of skills), but that is incremental rather than compensating for a gap.

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?

The opening sentence names a specific verb and resource ('List the published Mzizi agent skills, or fetch one in full') and immediately states what a skill is ('what an agent loads first'). It is clearly separable from siblings like mzizi_get_doctrine, mzizi_get_tokens, or mzizi_search, which cover different resource types.

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?

It gives explicit invocation routing: `category` for every skill in a category, `name` for one skill, `name` plus `file` for a single shipped file. It also states a when-to-use rule ('load these before any dev work') and names the equivalent alternative surfaces (MCP resource URIs and `skill-<name>` prompts) so the agent can pick a channel.

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?