Discover built-in dashboard templates for generating Tableau workbooks. See available starting points like sales, OEE, finance, and marketing before creating a workbook.
Return the list of built-in dashboard templates TabGen can start from (sales, OEE, finance, marketing, etc.).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the output (a list of built-in templates) and their nature (built-in, starting points), but does not explicitly state that the operation is read-only or that it has no side effects. For a simple list operation, this is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that conveys the core purpose and examples with zero fluff. Every word earns its place, and it is easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with no output schema, the description fully covers what an agent needs: what the tool returns, that the templates are built-in, and that they serve as starting points. Nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so the schema trivially covers 100%. Per the baseline rule, a score of 4 is appropriate; the description adds no parameter-specific detail, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Return'), a precise resource ('list of built-in dashboard templates'), and names example categories (sales, OEE, finance, marketing). It clearly distinguishes from siblings like publish_to_cloud or generate_workbook, which are actions rather than listing operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage as a starting point for dashboard creation ('TabGen can start from'), and the examples suggest when an agent would consult it. It does not explicitly contrast with alternatives, but the tool's purpose is self-evident and the sibling tools perform different actions, so no exclusion is strictly needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.