Using the Keboola semantic layer safely

The Keboola MCP system prompt already documents the semantic-layer workflow (discover with search_semantic_context, inspect with get_semantic_context, validate_semantic_query, then query_data). This skill adds the one failure mode that workflow does not spell out.

The semantic layer already carries the physical mapping — use it, don't bypass it. A semantic-dataset returns its tableId and fqn; a semantic-metric returns its SQL. The business-facing display names (a field labelled Total Revenue, an entity Trips) are not the physical columns — they are labels on top of the definition. The failure is writing SQL from those labels instead of from the definition the tools already gave you.

The one rule