Research tools
The free knowledge tools — search Unreal Engine documentation, engine patterns, your ingested logs, and project relations.
Five free tools give your AI client grounded knowledge about Unreal Engine and your project. All of them cost nothing and work at zero balance.
| Tool | Needs project context? | For |
|---|---|---|
search_docs_code | no | Search curated Unreal Engine documentation |
search_patterns | no | Check an approach against known engine patterns and anti-patterns |
search_logs_temporal | yes | Search log events previously ingested by analyze_logs |
query_temporal_relations | yes | Traverse how entities in your project relate |
investigate_incident | yes | Investigate one incident across logs, relations, and docs |
The three project-scoped tools need team/project context — your AI client wires it via setup_spaghetti (see Teams and projects). The documentation and pattern searches work everywhere.
search_docs_code
Hybrid full-text and semantic search over curated Unreal Engine documentation.
Search the engine docs for how FTickFunction ordering works during level load.Optional: projectId (also search your project's code), includeGlobalDocs (default true), k result count (up to 50, default 10). Returns ranked chunks with their source paths.
search_patterns
Describe an intent; get the recommended engine approach and the anti-pattern to avoid, with rationale and a confidence score.
Is spawning actors in Tick a known anti-pattern? What's the preferred way?Optional: k (up to 20).
search_logs_temporal
Searches structured log events your project already ingested via analyze_logs — filterable by time window, severity, subsystem, build, and session.
Find PackageName warnings in my project's logs between June 1 and June 5, severity Warning.Optional filters: timeFrom/timeTo, buildId, severity[], subsystem[], sessionId, k (up to 100), includeIncidents (also return matched incident groups).
query_temporal_relations
Traverses the entity-relation graph built from your ingested logs — up to 3 hops, optionally as of a point in time.
What references the BP_EnemyMaster actor? Two hops, as of last Friday.Optional: relationTypes[], asOf, maxHops (up to 3).
investigate_incident
A bounded investigation loop that combines the tools above — logs, relations, documentation, and engine patterns — into one answer with a timeline and cited evidence.
Investigate the intermittent load-hitch our team saw in yesterday's build, subsystem Loading.Optional: timeFrom/timeTo, buildId, subsystem[].
Was this page helpful?