Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

knowledge_stats

Verify if your knowledge base writes took effect and identify which roots are reachable. Returns per-root state (ok, unconfigured, unavailable) and counts for lessons, inbox, and recipes.

Instructions

查看各知识库 root 状态与计数(只读状态报告)。

触发时机:需要了解知识库状态、确认写入是否生效或排查检索范围时调用。
查看各 root 状态(ok/unconfigured/unavailable)与 lessons/inbox/
recipes 计数;unconfigured 静默、unavailable 会带 _warning。本工具是
只读状态查询,不替代 verify_hou_api / get_houdini_help /
get_best_practices,也不替代目标 Houdini 版本的 live verification。

参数说明:
- scope: 可选 root 名;缺省/"all" 报告全部 root。

返回:{status:success, roots:[{name, state, path, priority, writable,
lesson_count, draft_count, published_count, inbox_count,
recipes_count}]};未知 scope → status=error + error.code=
ls_unknown_root。整体过 apply_response_cap。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses the read-only nature, status values (ok/unconfigured/unavailable), behavior for unconfigured roots (silent), warning suffix for unavailable roots, and error handling for unknown scope. It also notes it does not replace live verification.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized: core purpose first, then trigger conditions, details, parameter explanation, and return format. Every sentence adds value with no redundancy, making it efficient and easy to parse.

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?

Despite having no output schema, the description provides the complete return structure, status semantics, and error code. Combined with the parameter explanation, it is fully self-contained for a one-parameter, read-only tool.

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

Parameters5/5

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

The schema only lists 'scope' with no description. The description explains scope is optional, with default/'all' returning all roots, and defines the special value 'all'. This fully compensates for the 0% schema description coverage.

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 it views knowledge base root statuses and counts (read-only status report). It explicitly names the resource and differentiates itself from sibling tools like verify_hou_api, get_houdini_help, and get_best_practices.

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?

The description provides explicit trigger conditions (e.g., when you need to check knowledge base status, confirm writes, or troubleshoot retrieval scope) and explicitly lists what it does not replace, offering clear context for when to use this tool over alternatives.

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/ChengZiiii/opera-houdini-mcp'

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