Skip to main content
Glama
s3eidat

S3eidat Tools MCP

by s3eidat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create an Excel workbook (.xlsx)

ai_create_xlsx
Read-onlyIdempotent

Builds real Excel .xlsx workbooks from data with multiple sheets, formatted headers, column widths, number formats, live formulas, filters, frozen headers, and totals rows.

Instructions

Build a real Excel .xlsx file from data: one or more sheets, each with optional column definitions (header, key, width, numFmt) and rows given as objects or arrays. Bold shaded header, frozen header row and filter buttons (both on by default), column widths fitted to the content, Excel number formats (raw codes like "#,##0.00" or aliases: integer, number, percent, currency, usd, eur, gbp, date, datetime, time, text), strings starting with "=" written as live formulas (=SUM(B2:B9), =B2*C2, cross-sheet refs), ISO date strings written as real dates, and an optional totals row (SUM/AVERAGE/COUNT/MIN/MAX formulas). Up to 50 sheets and 1,000,000 rows per sheet. Formulas are calculated by Excel when the file is opened. Writes to "output" (default "workbook.xlsx" in the output folder) and returns the path and a summary of each sheet.

Input Schema

NameRequiredDescriptionDefault
titleNoWorkbook title (file properties, and the default file name).
authorNoAuthor in the file properties.
outputNoWhere to write the result: a file path, or a folder ending in "/". Default: the server output folder (a temp folder unless --out-dir is set).
sheetsYes
parseDatesNoWrite ISO date strings as Excel dates (default true).
returnBase64NoAlso return the output as base64 in the result (only for small files). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description explicitly says the tool writes an .xlsx file to output and returns the path. That is a direct contradiction of the read-only annotation, so behavioral transparency is scored 1 despite otherwise rich behavioral detail.

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 long but front-loaded and dense with useful details rather than filler. It packs many capabilities into a single paragraph, though it could be more scannable with separate sentences or bullets for formulas, formatting, and limits.

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?

Given the tool's complexity, the description covers the important call semantics: sheet structure, formatting defaults, formulas, date handling, limits, and return behavior. With no output schema, it usefully states that the result includes the path and a summary of each sheet.

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 high at 83%, so the schema already documents most parameters. The description still adds meaningful semantics beyond the schema, including the 50-sheet and 1,000,000-row limits, formula handling, date conversion behavior, and totals-row calculation behavior.

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?

The description states a specific verb and resource: building a real Excel .xlsx file from data. It clearly distinguishes this creation tool from the conversion/read sibling ai_xlsx_to_markdown and from ai_create_pptx by naming the exact output format.

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 description makes the tool's domain clear but never explicitly states when to use it versus alternatives or when not to use it. Usage is implied by the capabilities listed, such as creating workbooks with sheets, formulas, and totals, but no explicit routing guidance is given.

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