Skip to main content
Glama
Tableau Knowledge MCP

Tableau Knowledge MCP

Check Business Preferences

check_business_preferences
Read-only

Validate Tableau Business Preferences rules before an agent reads them: check line format, limits, duplicates, contradictions, field names, and workbook issues so every rule is followed.

Instructions

Check a Tableau Business Preferences file (the "# rule" lines Tableau's agent reads before it answers) so every line is one the agent will actually follow. Call it with no text first to get the rulebook: format, limits, wording rules, workbook preparation and how to test.

Checks: the "# " line format (a slip makes Tableau silently ignore the line), the limits (Tableau
Cloud: 50 rules and 8,000 characters per dashboard; Tableau Next: 30,000 per semantic model),
headers, duplicates, contradictions, thresholds without "use only this value", formatting rules
that would leak into queries, conversational lines, absences that can be over-read, ambiguous
ordering and averages, and missing baseline rules (query formatting, failure handling).

`target` (a dashboard, sheet, workbook or data source: id or description) also checks every
[Field] and "Field" the file names against the captions the agent will see in Tableau Knowledge,
with "did you mean" suggestions, and flags workbook problems (duplicate, generic or helper field
names). `product` is "cloud" or "next". Returns `ok` (no errors), `issues` by line, and stats.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_business_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
targetNo
productNocloud
graph_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only, non-destructive, open-world profile, and the description adds substantial context beyond them: concrete limits (50 rules / 8,000 chars on Cloud, 30,000 on Next), the failure mode where a malformed line is silently ignored, and the return shape (`ok`, `issues` by line, stats). It never contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the first-call instruction are front-loaded, and the check inventory is dense rather than padded. The long enumerated "Checks:" sentence is justified by the tool's breadth but is heavy to parse in one pass.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a complex validator: it explains what is checked, the per-product limits, the optional target-based field validation, and what comes back, and an output schema exists so return details are partly redundant anyway. The unexplained `graph_id` is the one gap an agent could stumble on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the load, and it does for three of four params: `text` as the rule file content, `target` as a dashboard/sheet/workbook/data source id or description that triggers field-caption validation with "did you mean" hints, and `product` as "cloud" or "next" with different limits. `graph_id` is never mentioned, leaving one parameter undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource: validating a Tableau Business Preferences file of "# rule" lines so the agent actually follows each one. It also names the domain objects it inspects (rules, headers, thresholds, [Field] references) and is clearly distinct from the graph/lineage siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes the first call ("Call it with no `text` first to get the rulebook") and explains what `target` and `product` add on subsequent calls. It gives strong in-workflow guidance but does not state when not to use it or point to any alternative, which is less critical here since no sibling overlaps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.