Skip to main content
Glama
Sign In
KitchenSink4AI

KitchenSink4XL

by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Excel Application (Hidden Instance)

xl_app
Destructive

Run Excel workbook operations—recalculation, pivots, PDF/PNG export, conversion, encryption, autofit, goal seek, and sparklines—in a private Excel instance.

Instructions

Needs Microsoft Excel on Windows: full recalculation, real pivot tables, PDF export, sheet render to PNG, format conversion, password encryption, exact autofit, goal seek, sparklines and the opens-clean check. Reads go through xl_read, and cell, format and structure edits through xl_edit, xl_format and xl_structure. Ops that change the workbook back it up first. These ops run in a private hidden Excel that this server starts and closes. They never attach to or change the user's own Excel, and a workbook the user has open in Excel is refused, not edited. Ops, one per line, as name(required; opt optional): what it does. path, backup and verify_com are not repeated; xl_help shows them:

  • recalculate(opt engine timeout_seconds allow_network): Recalculate every formula in a hidden Excel and save the results; a circular reference is named.

  • com_manage_pivot(action; opt name source_sheet source_range dest_sheet dest_cell rows columns filters values timeout_seconds allow_network): Create, refresh, delete or list real pivot tables through Excel.

  • com_export_pdf(output; opt scope sheet range_a1 overwrite timeout_seconds allow_network): Export to PDF via Excel's real renderer.

  • com_render_sheet(output; opt sheet range_a1 overwrite timeout_seconds allow_network): Render a sheet or range to a PNG exactly as Excel shows it; the workbook is not changed.

  • com_convert_format(output; opt format overwrite timeout_seconds allow_network): Convert the workbook to xlsx, xlsm, xlsb, xls, csv or ods with Excel's own Save As; the source is never overwritten.

  • com_save_with_password(password; opt current_password timeout_seconds allow_network): Encrypt the workbook with Excel's real password encryption; the password cannot be recovered, so keep the backup.

  • com_autofit(opt sheet columns rows timeout_seconds allow_network): True column and row autofit using Excel's real text metrics (the file tier can only estimate widths). More ops follow, in the same format, in the op parameter's description.

Input Schema

NameRequiredDescriptionDefault
opYesThe operation to run: an op listed in this tool's description, or one of these, in the same format: - com_goal_seek(target_cell, target_value, changing_cell; opt sheet save timeout_seconds allow_network): Excel's Goal Seek: adjust changing_cell until the formula in target_cell reaches target_value. - com_set_sparkline(opt action location source type sheet timeout_seconds allow_network): Create, clear, or list sparkline groups through Excel. - com_validate_opens_clean(opt password timeout_seconds allow_network): Open the file in a hidden Excel and report whether it opens without a repair prompt. - update_now(): Install the newer version the update notice named; call only when the user asks or agrees. - update_notices(action): Turn update notices on or off, or show their status (action).
argsNoThe op's arguments as an object. Include path (the workbook file) unless the op's line names other paths or the op reads no workbook; unknown keys are refused. xl_help lists every argument.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, and the description adds substantial behavioral context beyond them: operations run in a private hidden Excel instance, never attach to or change the user's own Excel, refuse workbooks the user has open, and back up workbooks before mutating operations. It also warns that password encryption is unrecoverable, conversion never overwrites the source, and rendering does not change the workbook, all of which align with the annotations.

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 safety and routing context is front-loaded, and the operation list is formatted one per line, which suits a 12-op umbrella tool. It is still lengthy and splits operation definitions between the main description and the op parameter description, requiring the agent to read both locations, so it is well structured but not maximally concise.

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 complex multi-op tool with no output schema, the description covers prerequisites, safety behavior, backup/refusal behavior, shared argument conventions, and most operation semantics. It does not describe the return shape for most operations, but the per-op lines and xl_help reference cover enough that critical invocation details are not missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description still adds meaningful op-specific argument semantics such as target_cell, target_value, changing_cell for goal seek, and output, scope, sheet, range_a1 for export/render operations. It also explains the shared args object convention: include path unless another path is named, unknown keys are refused, and xl_help lists every argument.

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 identifies this as the Excel application-level tool that runs operations in a real hidden Excel instance on Windows, then enumerates recalculation, pivots, PDF/PNG rendering, conversion, encryption, autofit, goal seek, sparklines, and opens-clean validation. It explicitly separates reads through xl_read and cell/format/structure edits through xl_edit, xl_format, and xl_structure, so the agent can distinguish it from siblings.

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?

It gives clear usage conditions: Microsoft Excel on Windows is required, and this tool is for operations that need real Excel such as full recalculation, real pivot tables, PDF export, and exact autofit. It also directs reads and edit operations to sibling tools and states that a workbook open in the user's Excel is refused, not edited. It does not explicitly discuss routing to xl_workbook or xl_help beyond argument lookup, so it is not perfect.

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