Skip to main content
Glama
xinhuagu

agent-wiki

by xinhuagu
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

wiki_admin

Administer and maintain a structured wiki: initialize workspace, validate manifest, rebuild indexes, run health checks, and generate evidence reports.

Instructions

Wiki administration and maintenance. Select action to control behavior:

  • init: Initialize a new knowledge base — creates wiki/, raw/, schemas/ directories and default templates.

  • config: Show current workspace configuration: directories, lint settings, search settings, entity templates.

  • format-check: Validate the portable OKF package manifest (agent-wiki.yaml), package inventory, and conformance findings against OKF v0.1.

  • rebuild: Rebuild index.md, timeline.md, code knowledge graphs, and optionally the vector index (when search.hybrid is enabled). Set evidence_report=true to also regenerate the evidence report and persist it to wiki/evidence-report.md as part of the rebuild. Set okf_report=true to persist evidence/okf-report.json.

  • lint: Run comprehensive health checks: contradictions, orphan pages, broken links, raw file integrity (SHA-256), synthesis page integrity. Set apply_fixes=true to auto-repair fixable issues.

  • evidence-report: Aggregate evidence-first telemetry into a corpus-level Markdown report (source coverage, lineage diagnostics, 4-week write trend, Phase 2b readiness gates). Set write=true to also persist the report to wiki/evidence-report.md.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAdministration action to perform
pathNo[init] Config root — where .agent-wiki.yaml is created (default: current directory)
workspaceNo[init] Separate workspace directory for wiki/, raw/, schemas/. If omitted, data goes in path.
apply_fixesNo[lint] If true, automatically fix auto-fixable issues (missing frontmatter → inject title/type/tags). Default: false.
writeNo[evidence-report] If true, persist the report to wiki/evidence-report.md in addition to returning it. Default: false.
evidence_reportNo[rebuild] If true, also regenerate the evidence report and persist it to wiki/evidence-report.md as part of the rebuild. Useful for keeping the dashboard fresh without a separate evidence-report call. Default: false.
okf_reportNo[rebuild] If true, regenerate the OKF package inventory/conformance report and persist it to evidence/okf-report.json. Default: false.

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

The description details behaviors for each action, such as creating directories, regenerating files, and auto-fixing issues. While it does not explicitly mention destructive potential or permissions, it gives sufficient context for expected outcomes.

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?

The description is organized with a clear introductory sentence and a bullet list of actions. It is relatively concise, though some action descriptions could be slightly trimmed without losing clarity.

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?

Given the tool's complexity (multiple actions and parameters), the description covers each action's purpose and relevant parameters adequately. Without an output schema, it still describes expected outputs (e.g., config shows configuration, evidence-report returns a report).

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?

With 100% schema coverage, the description adds significant value by explaining how each parameter modifies behavior (e.g., apply_fixes for lint, write for evidence-report, evidence_report and okf_report for rebuild). This goes beyond the schema's basic descriptions.

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 description clearly states the tool's purpose as 'Wiki administration and maintenance' and enumerates specific actions (init, config, format-check, rebuild, lint, evidence-report), distinguishing it from sibling tools that handle read/write/ingest operations.

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

Usage Guidelines4/5

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

The description provides explicit guidance for each action, including parameters and effects. However, it does not explicitly state when not to use this tool or compare with alternatives, leaving some room for ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xinhuagu/agent-wiki'

If you have feedback or need assistance with the MCP directory API, please join our Discord server