Retrieve paginated charts from Apache Superset to browse and select visualizations for reporting.
List charts from Apache Superset with optional pagination
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": "list_charts"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| page_size | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It only states 'List charts', implying read operation, but does not disclose default behavior (e.g., if pagination is omitted, does it return all charts?), rate limits, or result set limits. The description is too minimal for a mutation-free tool.
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?
One sentence, no wasted words. However, it is too brief for the tool's complexity, lacking essential details. Front-loaded with purpose, but sacrifices completeness. Could be longer to add value.
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?
Given no output schema and minimal annotations, the description fails to explain return format, default pagination behavior, how to get all charts, or error handling. A listing tool should specify whether pagination is required and if a subsequent call is needed for full data.
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?
Schema coverage is 0%, so description must compensate. It mentions 'optional pagination', alluding to page and page_size, but does not explain their semantics (e.g., zero-indexed, default values, maximum page_size). No additional meaning beyond parameter names.
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 clearly states the verb 'List', the resource 'charts', the source 'Apache Superset', and mentions optional pagination. It distinguishes itself from sibling tools like get_chart (singular) and other list tools (e.g., list_databases) by specifying the resource.
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?
No guidance on when to use this tool versus alternatives (e.g., get_chart for a single chart, or other list tools). The description only implies usage for listing charts with optional pagination but lacks when-not or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.