| name | verify-duckdb-function |
| description | Look up a DuckDB or spatial-extension function's real signature/behavior against the installed version instead of relying on recalled knowledge. Use before writing code or making claims about any DuckDB/ST_* function. |
Do not rely on recalled knowledge about DuckDB or spatial extension functions — verify against the installed version before making claims or writing code.
CLI — best for specific function lookups (includes full description, parameter docs, return type):
duckdb -c "LOAD spatial; SELECT function_name, parameters, parameter_types, return_type, description FROM duckdb_functions() WHERE function_name ILIKE 'ST_Buffer'"
duckdb -c "LOAD spatial; SELECT function_name, parameters, return_type FROM duckdb_functions() WHERE function_name ILIKE 'ST_%' ORDER BY function_name"
duckdb -c "LOAD spatial; SELECT function_name, description FROM duckdb_functions() WHERE description ILIKE '%voronoi%'"
gh api — best for browsing the full spatial function reference (always matched to the installed version):
DUCKDB_REF=$(duckdb --version | sed 's/v\([0-9]*\.[0-9]*\)\.[0-9]* (\([^)]*\)).*/v\1-\2/' | tr '[:upper:]' '[:lower:]') && \
gh api "repos/duckdb/duckdb-spatial/contents/docs/functions.md?ref=${DUCKDB_REF}" --jq '.content' | base64 -d