query_data

io.github.thyn-ai/algenta · Verify this server

Execute a structured query against connected data sources. Convert the user's question to a structured intent and call this tool — do NOT try to write SQL or parse column names yourself. The engine resolves column meaning from mathematical relationships and statistical structure only. It works on any dataset without configuration. The governed filter shape is a record-predicate contract over normalized rows, not a SQL predicate language, so it also applies to Redis and other non-SQL sources. Structural roles (use in metric.role): - derived_measure: the main financial/operational aggregate (revenue, spend, value) - base_measure: counts, quantities, discrete amounts - unit_measure: per-unit prices, rates - ratio: percentages, margins, fill rates (0-1 range) - metric: let the engine pick the best numeric column If clarification_required is true, or if confidence < 0.85, check the candidates list and ask the user to clarify. Never fabricate column names or SQL.