diff --git a/pages/advanced-algorithms/available-algorithms.mdx b/pages/advanced-algorithms/available-algorithms.mdx
index bf5f9648b..0a9d1c5fb 100644
--- a/pages/advanced-algorithms/available-algorithms.mdx
+++ b/pages/advanced-algorithms/available-algorithms.mdx
@@ -132,7 +132,34 @@ If you want to know more and learn how this affects you, read our [announcement]
 
 ## APOC mappings
 
-This table shows the mapping between APOC functions/procedures and their Memgraph equivalents. Use these mappings if you're familiar with Neo4j's APOC library.
+When switching from Neo4j to Memgraph, application code that calls `apoc.*` or `gds.*`
+procedures and functions would otherwise break, since Memgraph exposes the same
+functionality under different names. The aliases below serve as a drop-in replacement for
+those APOC and GDS calls, so you can migrate without changing your application code.
+
+This table shows the mapping between APOC functions/procedures and their Memgraph equivalents.
+Use these mappings if you're familiar with Neo4j's APOC library.
+
+### Inspecting configured mappings
+
+Memgraph loads callable aliases from the JSON file pointed to by the
+[`--query-callable-mappings-path`](/database-management/configuration) flag.
+To list every alias currently registered (including any custom mappings you
+add to that file), run:
+
+```cypher
+SHOW QUERY CALLABLE MAPPINGS;
+```
+
+The query returns three columns:
+
+- `alias_name: string` ➡ The name clients call (for example, `apoc.version`).
+- `source_name: string` ➡ The underlying Memgraph procedure or function the
+  alias resolves to (for example, `mgps.version`).
+- `type: string` ➡ Either `procedure`, `function`, or `unknown` if the source
+  cannot be resolved.
+
+Running `SHOW QUERY CALLABLE MAPPINGS` requires the `CONFIG` privilege.
 
 | APOC | Description | Memgraph equivalent |
 |-------------------------|-------------|---------------------|