> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-actions/luminapullallmds.md). # LuminaPullAllMds ## Description Pull all metadata from the primary server. This commands retrieves metadata about the current database from Lumina. IDA will calculate checksums for all non-trivial functions in the database and send it to Lumina. This information will be used to match and retrieve metadata, which will be automatically applied. Please note that this may overwrite your changes, so taking a database snapshot and saving the database before invoking this command is a good idea. By non-trivial functions we mean: * long enough functions (>=16 bytes) * non-library functions * non-imported functions (functions with real body) ### Lumina Metadata Metadata currently consists of the following information: * function address, name, prototype * function frame layout * stack variables * user-defined sp change points * representation of instruction operands * function and instruction comments --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hex-rays.com/ida-actions/luminapullallmds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.