Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

get_best_practices

Search Houdini advisory recipes by query, category, or ID to find solutions for common issues from the local knowledge base.

Instructions

查询 fork 人工审查的 BEST_PRACTICES advisory recipes(bridge-local)。

本工具 **不建立 Houdini TCP 连接**,直接在 bridge 进程内加载并查询
BEST_PRACTICES.md。recipe 是 advisory,不替代 verify_hou_api /
get_houdini_help,也不替代目标 Houdini 版本的 live verification。

参数说明:
- query: 可选,对 problem/symptom/fix/category/source 做 casefold
  子串匹配。
- category: 可选,精确匹配 category 字段。
- id: 可选,精确匹配 recipe id(如 "BP-001")。
多个参数组合为 AND。

返回统一 envelope:status(success/error)、practices(实际返回列表)、
total_indexed(过滤前索引数)、matched_count(过滤命中数)、
returned_count(cap 后实际返回数,恒等于 len(practices))、truncated
(matched > returned 时为 true)。error 时 error={code,message,details},
且 practices 为空、三个 count 为 0。响应整体过 apply_response_cap。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
ctxYes
queryNo
categoryNo
Behavior5/5

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

With no annotations provided, the description carries full burden and does an excellent job. It discloses bridge-local operation, no Houdini TCP connection, loading of BEST_PRACTICES.md, advisory nature, and detailed response envelope including error behavior, counts, and truncation flag. This is far beyond minimal disclosure.

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 structured with clear sections: purpose, exclusions, parameter details, and return envelope. Every sentence adds meaningful information with no fluff. The use of formatting aids readability without unnecessary length.

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?

The description comprehensively covers behavior, parameter semantics (except ctx), error responses, and response fields, which is especially important with no output schema. The only gap is the unexplained required ctx parameter, so it falls just short of complete.

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?

Even though schema coverage is 0%, the description adds rich semantics for query (casefold substring match), category (exact match), and id (exact match), and explains AND combination. However, the required ctx parameter is entirely undocumented, which prevents a perfect score.

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 queries fork-reviewed BEST_PRACTICES advisory recipes locally in the bridge. It explicitly says it does not establish a Houdini TCP connection and distinguishes it from verify_hou_api/get_houdini_help, making the purpose specific and unambiguous.

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 when-not guidance: recipes are advisory and do not replace verify_hou_api/get_houdini_help or live verification. This names alternatives and clarifies the tool's scope, which is exactly the kind of usage guidance required.

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