preset-mcp

get_chart

Retrieve chart details including visualization type, parameters, and query context by providing a chart ID. Use list_charts to obtain valid IDs.

Instructions

Get detail for a single chart including params and query context.

Returns the chart's visualization type, parameters, query_context, datasource info, and other metadata. Use list_charts first to find valid IDs.

Args: chart_id: Numeric chart ID response_mode: 'compact' (id+name+viz_type), 'standard' (key fields), or 'full' (raw API response). Default: full.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chart_id": "<chart_id>"
    },
    "name": "get_chart"
  }
}

Input Schema

Name	Required	Description	Default
`chart_id`	Yes
`response_mode`	No		full

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 8, 2026

TDQS

A4.1/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden. It does not disclose behavioral traits such as whether the operation is read-only, idempotent, what errors might occur, or any rate limits. It only describes the return data, not the behavior or side effects.

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?

The description is succinct and well-structured: a two-sentence summary, a bullet list of return fields, a usage note, and a clear args section. Every sentence serves a purpose, with no redundancy.

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?

For a simple retrieval tool with two parameters and an output schema, the description covers the return values, usage, and parameters adequately. However, it lacks information about error handling or prerequisites beyond 'list_charts first,' which could be beneficial.

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

Parameters5/5

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

Schema description coverage is 0%, but the description adds significant meaning: it describes chart_id as 'Numeric chart ID' and explains response_mode values ('compact', 'standard', 'full') with what each returns, including a default of 'full'. This fully compensates for the lack of schema descriptions.

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?

Description clearly states the tool retrieves details for a single chart, listing specific return fields (visualization type, parameters, query_context, datasource info, other metadata). It also mentions to use list_charts first, distinguishing it from sibling tools like list_charts, create_chart, etc.

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?

Provides a clear usage hint: 'Use list_charts first to find valid IDs.' Explains the three response modes. However, does not explicitly state when not to use this tool or mention alternatives besides list_charts.

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

Deploy Server