Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Generate Spreadsheet

generate_spreadsheet
Read-onlyIdempotent

Draw a table as an image, or a pivot table when rows/values are given (cross-tabulation, sums by category). Data [{...}] objects with the same fields; rows, columns and values name the fields to pivot. For an Excel file use the Excel link any chart tool returns. Returns a hosted PNG link, a share page, alt text and editable PowerPoint/Excel links.

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

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes beyond them by naming the returned artifacts: hosted PNG link, share page, alt text, and editable PowerPoint/Excel links. It also flags the brandTheme constraint ('only when the user asks for their theme'), which is behavior an agent would otherwise get wrong. It does not discuss size limits or failure modes for large datasets.

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?

Three tight sentences that front-load the primary purpose and output, with zero filler. The pivot condition is stated twice (in the opening clause and again in the rows/columns/values sentence), which is mildly redundant against the schema but aids scanning.

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 an 8-parameter generative tool with no output schema, the description carries the important load: what is rendered, how pivot mode is triggered, and what comes back. Remaining gaps (size/format limits, how the share page differs from the PNG) are minor for a read-only renderer.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning on top: it explains that rows/values name the pivot fields and that columns also drives column ordering versus group headers. The brandTheme note restricts usage to a user-requested theme, a rule the schema text only partially conveys.

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?

States a specific verb and resource ('Draw a table as an image') plus the alternate mode ('a pivot table when rows/values are given'), so an agent knows exactly what artifact comes out. It does not explicitly contrast itself with the many chart siblings, but the table/pivot framing makes the resource type unmistakable.

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?

Gives a concrete selection rule inside the tool (plain table vs pivot when rows/values are supplied) and a redirect for the Excel case ('for an Excel file use the Excel link any chart tool returns'). It stops short of saying when to pick this over generate_bar_chart or generate_dashboard, leaving cross-tool choice to inference.

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