Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

get_doc

Retrieve full text of indexed documentation by relative path, offline, no Houdini connection needed. Returns exact content from the index.

Instructions

按相对路径取回已索引文档的全文(bridge-local,无 Houdini 连接)。

本工具 **不建立 Houdini TCP 连接**,``path`` 只与已校验索引中的规范
化 POSIX 相对 path 做精确匹配,全文从 JSON 内嵌 content 返回,
**绝不拼接源文件系统路径或回读索引外文件**(含 ``..`` 遍历串)。
与 ``get_houdini_help`` / ``verify_hou_api`` 互补:那两个面向在线
结构化字段查询,本工具面向已索引离线文档的整篇读取。

参数说明:
- path: 索引中文档的 POSIX 相对路径(如 ``nodes/sop/box.html``),
  可先用 search_docs 取得。

返回统一 envelope:status(success/error)、path、title、length、
content(全文,过 apply_response_cap)、returned(1 命中 / 0 未命中)。
path 不存在或非法返回 rag_doc_not_found;索引缺失 / 损坏分别返回
rag_index_missing / rag_index_unavailable。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxYes
pathYes
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses that no Houdini TCP connection is made, that path matches exactly against normalized POSIX relative paths, that it never concatenates source filesystem paths or reads files outside the index (including .. traversals), and it details the return envelope and error codes (rag_doc_not_found, rag_index_missing, rag_index_unavailable). This is far more than typical.

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 clearly separated sections for purpose, safety behavior, sibling distinction, parameter details, and return envelope. It is long but every sentence provides valuable information; no filler or repetition.

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 covers the tool's behavior, return format, and error conditions thoroughly. The only notable gap is the unexplained `ctx` parameter, which prevents it from being fully complete. Overall it's nearly comprehensive for a retrieval tool.

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?

The description thoroughly explains the `path` parameter with format, example, and how to obtain it. However, the required `ctx` parameter is not described at all. Since schema has 0% parameter descriptions, the description only partially compensates, leaving the agent guessing about `ctx`.

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 '按相对路径取回已索引文档的全文' (retrieve full text of indexed document by relative path), giving a specific verb, resource, and scope. It explicitly distinguishes itself from get_houdini_help and verify_hou_api as complementary tools, making sibling differentiation strong.

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 explicitly explains when to use this tool vs alternatives: states that get_houdini_help / verify_hou_api target online structured field queries, while this tool is for offline indexed documents. It also notes that search_docs can be used to obtain the path, guiding the agent to the prerequisite.

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