Kibi

Overview Schema Source Related Servers Discussions Admin

kb_skills

Read-onlyIdempotent

Read bundled Kibi agent skills and workflow guidance: list the catalog, load a skill's metadata and Markdown body, or read a declared resource. Read-only and no Prolog required.

Instructions

Read bundled Kibi agent skills (workflow guidance). action:list returns the catalog; action:load returns a skill's metadata, Markdown body, declared resources and content hash (start with id 'kibi-usage'); action:read returns one manifest-declared resource. Read-only; does not require Prolog.

Input Schema

Name	Required	Description
`id`	No	Bundled skill ID. Example: 'kibi-usage'.
`action`	Yes	list, load (needs id) or read (needs id and resource).
`resource`	No	Manifest-declared resource path to read. Example: 'resources/workflows.md'.
`workspaceRoot`	No	Optional absolute path of the workspace this call is about when it differs from the one the server started in, for example the git worktree you are working in. The server answers from that workspace's knowledge base when it is a worktree of the same repository or lies under the client's MCP roots; otherwise it answers from its own workspace and adds a workspace_mismatch diagnostic. Host hooks fill this in automatically where available.

Output Schema

Name	Required	Description	Default
`data`	Yes
`error`	No
`status`	Yes
`effects`	Yes
`operation`	Yes
`diagnostics`	Yes
`nextActions`	Yes
`kibiProtocol`	Yes
`resultVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/non-open-world, so the bar is lower; the description still adds that no Prolog engine is required (a real prerequisite for other kb tools) and roughly what each action yields. It stops short of rate limits, caching or workspace-resolution nuance, which the schema handles instead.

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?

A single dense, front-loaded sentence enumerating the actions plus one short constraint clause; every clause earns its place. Slightly run-on with three semicolon-joined action definitions, but no filler.

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 annotations, a 100%-covered schema and an output schema present, the description only needs to cover purpose, action routing and the Prolog-free constraint, and it does all three. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds function-level meaning to the action values beyond the schema's const list (what 'load' returns vs 'read' vs 'list') and names a concrete starting id. It adds nothing for workspaceRoot or resource beyond what the schema already explains.

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+resource ('Read bundled Kibi agent skills') and then disambiguates its three actions by what each returns (catalog, metadata/Markdown body/resources/hash, single manifest resource). An agent can distinguish this from kb_query/kb_search without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an in-tool sequencing hint ('start with id kibi-usage') and context ('workflow guidance', 'Read-only; does not require Prolog'), but never says when to prefer this tool over siblings like kb_search, kb_query or kb_graph, nor any when-not condition.

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

Deploy Server