Skip to main content
Glama
Tableau Knowledge MCP

Tableau Knowledge MCP

Graph health

graph_health
Read-only

Assess a Tableau knowledge graph's health using a 0–100 score, semantic coverage and graph metrics, plus categorized improvement suggestions with severity and target node IDs.

Instructions

Graph-health report: a 0-100 health_score, coverage metrics (e.g. how many nodes carry semantic context), graph stats, and concrete improvement suggestions (each with severity, recommended_action and the target node ids), grouped by category and topic.

`pds_id` scopes the report to one published data source's subtree. `severity` ("high",
"medium", "low"), `suggestion_type` and `limit` (default 20; a busy graph has hundreds) filter
only the suggestion lists; the score, metrics and `summary` totals always cover the full (or
PDS-scoped) graph.

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": "graph_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
pds_idNo
graph_idNo
severityNo
suggestion_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the readOnly/non-destructive annotations: it defines the 0-100 score, explains that filters apply only to suggestion lists while score/metrics cover the full graph, and notes the default limit against a busy graph with hundreds of suggestions. These are non-obvious semantics that prevent misinterpretation of results.

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

Conciseness5/5

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

Two tight paragraphs, front-loaded with what the tool returns and followed by scoping/filter semantics. Every sentence adds distinct information; nothing is repeated from the schema or annotations.

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?

The description is thorough about output structure and filter behavior, and the presence of an output schema reduces the need to explain return values further. The missing explanation of graph_id and its relationship to pds_id is the only notable gap for a five-parameter tool.

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?

With 0% schema description coverage, the description carries the full burden and explains four of five parameters: pds_id scoping, severity allowed values, suggestion_type filtering, and limit default/scale. graph_id is completely undocumented, leaving one parameter's purpose and interaction with pds_id undefined.

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?

The description names a specific report resource and enumerates its contents (health_score, coverage metrics, graph stats, suggestions), making it unmistakable what the tool returns. No sibling tool produces a health report, so the distinction is inherent even without an explicit comparison.

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?

The report context is clear enough that an agent knows to use this tool when assessing graph health, and the second paragraph gives explicit guidance on how scoping and filtering work. It stops short of naming alternatives or stating when not to use it, but for a unique health-report endpoint no alternative exists.

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