Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Export Range

export_range
Destructive

Export Excel ranges, tables, or sheets to CSV, TSV, or JSON with cached or formula values, writing to a file or returning text inline.

Instructions

Export a range, table, or sheet to CSV, TSV, or JSON. location defaults to the true used range; {table} exports a table. values is cached | formula | both; the result states the mode used. out_file writes a file; otherwise text returns inline. The target is guarded: never the source workbook, a workbook extension, a reserved device name, or .ks4xl-backups; an existing file needs overwrite, which keeps a .bak first. Filter-hidden rows export like any other row. Multi-sheet is export_file, io pack. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fmtNocsv
pathYes
sheetNo
headerNo
valuesNocached
recordsNo
locationNo
out_fileNo
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv1.1.0
    • addedInput schema / properties / location / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / location / title
      Removed value: -"Location"
  3. First observedv1.0.0

TDQS

A3.5/5.0
Behavior1/5

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

The description ends with 'Read-only', but annotations set destructiveHint: true, which is a direct contradiction. The description also details overwriting existing files with a .bak backup, which implies destructive behavior. This inconsistency is a serious transparency failure.

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 dense and information-rich, with each sentence adding a distinct point. It avoids fluff and organizes content logically from action to parameters to safety. While slightly long, it remains efficient.

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?

Despite covering many behaviors, the contradiction with annotations ('Read-only' vs destructiveHint: true) creates a major gap. There is no mention of the inline return format or error handling, and no output schema to fill the gap. For a 9-parameter tool, this is incomplete.

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?

With 0% schema description coverage, the description compensates by explaining key parameters: location (defaults to true used range), values (cached|formula|both), out_file (file vs inline), and the target guard. However, it omits details for fmt, sheet, header, records, and path, leaving some parameters under-specified.

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?

States a specific verb (export) and resource (range, table, sheet) along with output formats (CSV, TSV, JSON). It also distinguishes behavior for tables and defaults for location, making the tool's purpose clear and distinct from siblings like read_range or get_cells.

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 guidance on parameter usage (location defaults, values modes, out_file vs inline) and notes that multi-sheet exports use a different tool (export_file, io pack). It does not explicitly contrast with similar read tools, but the export purpose is inherently distinct.

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

Deploy Server

Other Tools