Tableau's Solutions Engineer and Market Strategy Lead: AI Agent Accuracy Depends More on Setup Than on the Model
Will Pitzler and Andrew Hill describe six configuration and governance practices that took custom Tableau MCP agents from prototype to production for a regulated enterprise customer, arguing that scoping, metadata preparation and evaluation discipline matter more than model choice.
Will Pitzler, Senior Director of Market Strategy and Ecosystem at Tableau, and Andrew Hill, a Distinguished Solutions Engineer at Tableau, describe a customer engagement in which the team learned that an agent's accuracy depends far more on how it is configured, scoped and maintained than on which model it runs. Their customer, a large enterprise in a highly regulated industry, needed agents that could answer specific questions from Tableau data and act on those answers without leaving the agent environment. The stakes were high: in a regulated context, acting on a wrong answer can become a compliance issue, not just an inconvenience.
Tableau offers ready-to-use agents like Tableau Agent and Tableau Agent in Pulse, which are tightly scoped to improve accuracy out of the box. But this customer needed more: specialized workflows where accuracy was paramount, agentic workflows that let users act on findings without leaving the agent, embedding outside Tableau in a purpose-built application, fine-grained developer control over data access and tool permissions, and proof before production. This led them to build custom agents with Tableau MCP, which gives control that a ready-to-use agent cannot, but demands more rigorous testing, tighter governance and ongoing monitoring.
The first practice applies to any agent, ready-to-use or custom: prepare the data model. Any agent can only be as accurate as the data model it reads. The authors recommend putting business logic as close to the data as possible. If logic can be written as a calculation, write a calculated field so it gives the same answer each time rather than leaving it to agent interpretation. For example, Open Pipeline should be defined as IF NOT [Stage] IN ('Closed Won', 'Closed Lost') THEN [Opportunity Amount] END. Logic that every agent should know goes into Tableau Knowledge business preferences or field descriptions. Logic that applies to only one agent goes into that agent's system instructions. They also recommend removing field duplicates, describing fields with units and caveats, naming fields based on business logic rather than database names, hiding irrelevant fields like join keys, and certifying the data sources the agent is allowed to rely on.