search_godot_docs
Find Godot documentation pages, tutorials, and class reference entries by keyword or question. Returns ranked matches with links and identifiers, so you can fetch the right doc or inspect a class member.
Instructions
Search the Godot documentation -- manual, tutorials, and class reference -- and return ranked matches. Start here whenever the exact class or page is not already known. Natural-language questions work as well as keywords: framing words are stripped before searching, so 'how do I make a character jump' finds the tutorial rather than every page titled 'How do I'. Follow a hit with its own fields: uri is what fetch_godot_doc takes, and a hit from the class reference also carries class_name and member_name, which are what get_godot_class and get_godot_class_member take. At most one hit is returned per page or class; also_matched counts the further matches on that same source that were folded into it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Restrict results to one part of the documentation. | |
| limit | No | Maximum results to return. Values above 50 are reduced to 50 rather than rejected. Fewer may come back: the response is also capped by total size. | |
| query | Yes | What to look for, in plain words. A question is fine. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | What to call next to see what was omitted, or to narrow the request. Empty when nothing was left out. | |
| hits | No | Matches, best first, at most one per page or class. | |
| query | Yes | The query as it was actually searched, which may differ from what was asked when question phrasing was stripped out. | |
| notice | No | An advisory about the index itself -- that a newer one has been published, for instance. It says nothing about the hits, which are as correct for the indexed version as they ever were. Empty when there is nothing to report. | |
| truncated | No | Whether content was omitted to stay within the budget. |