Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Generate Spreadsheet

generate_spreadsheet
Read-only

Generate a spreadsheet or pivot table for displaying tabular data. When 'rows' or 'values' fields are provided, it renders as a pivot table (cross-tabulation); otherwise, it renders as a regular table. Useful for displaying structured data, comparing values across categories, and creating data summaries.

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": {
      "data": "<data>"
    },
    "name": "generate_spreadsheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData for spreadsheet, an array of objects where each object represents a row. Keys are column names and values can be string, number, or null. Such as, [{ name: 'John', age: 30 }, { name: 'Jane', age: 25 }].
rowsNoRow header fields for pivot table. When 'rows' or 'values' is provided, the spreadsheet will be rendered as a pivot table.
themeNoSet the theme for the spreadsheet, optional, default is 'default'.default
widthNoSet the width of chart, default is 600.
heightNoSet the height of chart, default is 400.
valuesNoValue fields for pivot table. When 'rows' or 'values' is provided, the spreadsheet will be rendered as a pivot table.
columnsNoColumn header fields, used to specify the order of columns. For regular tables, this determines column order; for pivot tables, this is used for column grouping.
brandThemeNoName of a brand theme saved on the user's account (their colours and footer), only when the user asks for their theme. Or "colorblind" for colours that people with colour-vision deficiency can tell apart (anyone can use it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The readOnlyHint already tells the agent this is a non-mutating generation tool. The description adds meaningful behavioral context beyond that: providing 'rows' or 'values' changes the output from a regular table to a cross-tabulated pivot table. It does not describe the final output format, such as whether the result is an image, HTML, or a configuration object, which leaves one behavioral gap.

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 front-loaded with the core action and the pivot-versus-regular-table rule, and it uses only three sentences. The final sentence about displaying structured data, comparing categories, and creating summaries is somewhat generic and could be tightened, but it is not a major distraction.

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

Completeness3/5

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

The description covers the tool's main purpose and its pivot-table branching, which is appropriate given the rich input schema. However, with eight parameters and no output schema, it leaves the agent without a description of what 'generate' returns or how the rendered result is consumed. That is a meaningful completeness gap for a visualization-generation tool.

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?

Schema description coverage is 100%, so the schema already documents all eight parameters. The description reinforces the important parameter relationship that 'rows' or 'values' triggers pivot mode, which adds some meaning beyond individual field descriptions, but it does not explain the roles of theme, width, height, columns, or brandTheme. This fits the baseline of 3 when the schema carries the detailed 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: 'Generate a spreadsheet or pivot table for displaying tabular data.' It also explains the two rendering modes, so an agent can distinguish a tabular-output tool from the sibling chart-generation tools. It stops short of explicitly naming or contrasting those siblings, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

It gives implied usage guidance by saying the tool is 'useful for displaying structured data, comparing values across categories, and creating data summaries,' and it explains that 'rows' or 'values' triggers pivot rendering. However, it does not say when not to use it or explicitly route the agent to an alternative chart tool for non-tabular displays.

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

All ChartAnt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources