Documentation for building, running, deploying, and troubleshooting Holon.
Scored across 1 tool
With a single tool there is nothing to confuse it with; its purpose of opening Holon documentation is unambiguous.
The lone name open_docs follows a clean verb_noun snake_case convention with no competing styles to conflict with.
A single trivial tool is very thin for a documentation server; there is no way to search, list sections, or fetch specific topics, so one generic opener under-serves the purpose.
The surface only offers a blanket 'open docs' action, with no topic lookup, search, or installation-specific retrieval, leaving agents with dead ends for anything but the entry point.
Open Holon documentation and installation instructions.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | docs |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already tells the agent this is a safe read. The description adds only that the content is documentation and installation instructions; it says nothing about whether the tool launches an external viewer, what form the response takes, or whether network access is needed. With annotations carrying the safety profile, this is a modest contribution rather than a gap-free one.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short, front-loaded sentence with no filler. It is efficient, though brevity here comes at the cost of the missing parameter explanation rather than being paired with it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a low-complexity, no-output-schema tool, so the description does not need to explain return values. However, it omits the one piece of information an agent actually needs to call it correctly: the meaning of the 'docs' and 'access' page options.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry the weight for the single 'page' parameter, and it does not. 'docs' is loosely implied by 'documentation,' but the 'access' enum value is never mentioned, leaving the agent to guess between two options.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource: 'Open Holon documentation and installation instructions.' An agent can tell broadly what the tool fetches, though it never clarifies what 'open' means (display a URL vs. return content) or what the 'access' page contains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool or which page value to choose. With no siblings, sibling routing is moot, but the docs-vs-access choice is left entirely unexplained.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
open_docsMedius docs: the binary control protocol, device behavior, and the medius Rust library.
Read-only docs for the Accordo CRM framework: what it proves, and where it stops.
Read-only HotAPI documentation: search integration guides and inspect OpenAPI operations.
Build, test, deploy, and operate Connic agents.
Add one secure layer between your agents and this server.
