Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Excel Create

excel_create

Creates a new Excel spreadsheet (.xlsx file) with headers and optional data rows. JSON numbers (integers and decimals) are written as numbers, so SUM() and charts work on them; JSON strings always stay text even when they look numeric ("007", "1e3", or " 42"), as do integer values longer than 10 digits because they are identifiers like a CUIT, CBU or phone number rather than quantities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesOutput path for the .xlsx file
rowsNoArray of ROW ARRAYS — each row is itself an array of cell values (optional)
confirmNoMust be true to create
headersYesColumn headers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath of the created .xlsx file
rowsYesNumber of data rows written
createdYesTrue when the file was created
headersYesColumn headers written

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / rows / description
      Previous value: -"Array of row arrays with data (optional)"New value: +"Array of ROW ARRAYS — each row is itself an array of cell values (optional)"
    • addedInput schema / properties / rows / items
      Added value: +{
+  "description": "One row: the cell values, in column order",
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / rows / description
      Previous value: -"Array of ROW ARRAYS — each row is itself an array of cell values (optional)"New value: +"Array of row arrays with data (optional)"
    • removedInput schema / properties / rows / items
      Removed value: -{
-  "description": "One row: the cell values, in column order",
-  "type": "array"
-}
  3. Changed2 schema fields changed
    • changedInput schema / properties / rows / description
      Previous value: -"Array of row arrays with data (optional)"New value: +"Array of ROW ARRAYS — each row is itself an array of cell values (optional)"
    • addedInput schema / properties / rows / items
      Added value: +{
+  "description": "One row: the cell values, in column order",
+  "type": "array"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing important type-coercion behavior: JSON numbers stay numeric for SUM()/charts, JSON strings stay text even when numeric-looking, and long integer identifiers like CUIT/CBU/phone numbers are preserved as text. This is exactly the kind of behavioral nuance an agent needs to avoid data corruption. No contradiction with the annotations exists.

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 sentences with no filler. The first sentence front-loads the core purpose and file type; the second delivers high-value behavioral detail about numeric handling. Every clause earns its place and the text is easy to scan.

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 create operation, the description covers purpose, file format, optional rows, and key type behavior. The schema already documents the confirm flag and row-array shape, so those gaps are covered. One minor omission is whether an existing file at the given path is overwritten or causes an error, which could matter for an agent deciding how to proceed.

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. The description adds meaningful value beyond the schema by explaining how row values will be interpreted (numbers vs. strings vs. long identifiers), which directly informs how the agent should construct the 'rows' parameter. This compensates for the schema's terse 'cell values' description.

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: 'Creates a new Excel spreadsheet (.xlsx file) with headers and optional data rows.' This clearly distinguishes it from sibling tools like excel_read and excel_write_cell, which operate on existing files/cells rather than creating a new workbook.

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?

The purpose 'creates a new Excel spreadsheet' implies when to use this tool (new .xlsx file creation), but the description provides no explicit when-not-to-use guidance or alternatives. It does not mention that modifications to an existing spreadsheet should use excel_write_cell or that generic file creation might use file_write. The usage context is implied rather than stated.

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

All Local MCP 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