quicksight-mcp

create_kpi

Build a KPI visual in QuickSight from column, aggregation, and title parameters. Use to add metric cards to analysis sheets.

Instructions

Create a KPI visual from simple parameters.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Display title (e.g., "Total Contracts").
`column`	Yes	Column name (e.g., "FLIP_TOKEN").
`sheet_id`	Yes	The sheet to add the KPI to.
`aggregation`	Yes	SUM, COUNT, AVG, MIN, MAX, or DISTINCT_COUNT.
`analysis_id`	Yes	The QuickSight analysis ID.
`format_string`	No	Display format (e.g., "#,##0", "$#,##0.00", "0.0%"). Leave empty for default formatting.
`conditional_format`	No	JSON string of color rules. Example: '[{"condition": ">= 100", "color": "#2CAF4A"}, {"condition": "< 50", "color": "#DE3B00"}]' Leave empty for no conditional formatting.
`dataset_identifier`	Yes	The dataset identifier.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers almost none. It implies a mutation ('Create'), yet does not state required permissions, side effects, whether the KPI is added to an existing sheet, or any failure modes.

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?

The description is a single, front-loaded sentence with no wasted preamble. While 'from simple parameters' is somewhat vague filler, the overall structure is efficient and easy to scan.

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

Completeness2/5

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

For a mutation tool with no annotations and eight parameters, the description is too thin. Although an output schema exists and the input schema is fully documented, an agent still lacks context about what a KPI visual is, where it gets placed, or what prerequisites exist beyond the schema fields.

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

Parameters3/5

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

The input schema has 100% description coverage, so the baseline is 3. The description adds no meaning beyond what the schema already provides for the eight parameters; 'simple parameters' is not parameter semantics.

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

Purpose4/5

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

The description states a specific verb and resource: 'Create a KPI visual', which clearly identifies the action and the artifact. It distinguishes this tool from sibling visual creators like create_bar_chart or create_line_chart by naming the KPI type, though it does not explicitly contrast them or clarify scope.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as add_visual or other create chart tools. No prerequisites, conditions, or exclusions are mentioned; the phrase 'from simple parameters' provides no actionable selection criteria.

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

Deploy Server