Excel MCP Server

Import CSV

import_csv

Destructive

Import a CSV or TSV file into an Excel sheet starting at a chosen cell, overwriting existing cells. Converts numbers, TRUE/FALSE and ISO dates to values while keeping leading zeros and formulas as text.

Instructions

Import a CSV file into a sheet from at, overwriting cells.

Numbers, TRUE/FALSE and ISO dates become values; leading zeros ('007'), over 15 digits and ambiguous dates stay text. Never formulas: text starting with = + - @ is text.

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": {
      "path": "<path>",
      "csv_path": "<csv_path>",
      "sheet": "<sheet>"
    },
    "name": "import_csv"
  }
}

Input Schema

Name	Required	Description	Default
`at`	No	Top-left cell.	A1
`path`	Yes
`sheet`	Yes	Created if missing.
`as_text`	No	Keep every field as text.
`decimal`	No	Decimal mark; the other groups thousands.	.
`csv_path`	Yes	.csv or .tsv file, located like workbooks.
`encoding`	No	'utf-8' also reads a BOM.	utf-8
`delimiter`	No	'auto': most frequent in the first record.	auto
`date_order`	No	'dmy' or 'mdy' also read 31/12/2026-style dates; else only ISO ones are dates.	ymd

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.2.1Oct 19, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already disclose that the tool is destructive, non-read-only, and non-idempotent. The description adds meaningful behavioral context by specifying that cells are overwritten and by detailing type coercion and formula-handling rules, though it does not cover auth, errors, or return behavior.

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?

Two tightly written sentences with no filler. The core action and overwrite behavior are front-loaded, followed by the high-value conversion rules.

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 9-parameter destructive import tool with no output schema, the description covers purpose, overwrite behavior, and important type-conversion semantics. Annotations carry the safety profile, and the schema covers most parameters, so only minor details such as error handling or header treatment are absent.

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 description coverage is high at 89%, so the baseline is 3. The description adds useful semantic detail beyond the schema: numbers, booleans and ISO dates become values; leading zeros, >15-digit values and ambiguous dates stay text; formula-like text is never evaluated. This clarifies how parameters such as as_text and date_order affect parsing.

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 and resource ('Import a CSV file into a sheet') plus scope ('from `at`, overwriting cells'). This distinguishes it from siblings like export_csv and import_workbook without needing to name them.

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

Usage Guidelines2/5

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

The description says what the tool does but gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as import_workbook or write_range. Usage is only implied by the tool name and purpose.

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