Retrieve the relevant documentation section by heading title, letting you access targeted Minecraft Forge/NeoForge modding information without scanning the full page.
Read a specific section of a documentation page by heading title.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Document path relative to docs root | |
| section | Yes | Section heading to extract (partial match supported) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The word 'Read' indicates a non-destructive operation, and 'by heading title' explains the selection mechanism. However, with no annotations, the description leaves behavioral context unstated, such as behavior when the heading is missing, whether partial matches are allowed in practice, or any access limitations.
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?
The description is a single, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and lookup mechanism.
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?
For a simple read operation with two well-documented parameters, the description is mostly sufficient. However, it does not clarify how this differs from the closely related get_document, and with no output schema, the description does not indicate what form the returned section content takes.
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 100%, so the schema already documents both parameters well. The description's phrase 'by heading title' aligns with the section parameter but does not add significant meaning beyond what the schema already provides.
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 states a specific verb ('Read') and resource ('a specific section of a documentation page') with a clear lookup mechanism ('by heading title'). This distinguishes it from the sibling get_document, which reads a whole page, even without naming the alternative.
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 versus related siblings such as get_document, search_docs, or list_documents. The description only states what the tool does, not when it should be chosen or when a sibling would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.