Skip to main content
Glama
leanzero-srl

MCP Document Processor

Official
by leanzero-srl

create-excel

Generate styled Excel (XLSX) or CSV spreadsheets for budgets, datasets, and reports. Supports formulas, auto-format, and zebra striping.

Instructions

Create a styled Excel XLSX (or CSV). USE for ANY tabular/numeric data — budgets, trackers, datasets, KPIs, price lists, schedules; even a table inside a 'report' belongs here, not in a doc. EXCEL SUPERPOWERS: a cell whose string starts with '=' becomes a LIVE formula (e.g. "=SUM(B2:B9)", "=B2C2") that Excel computes on open; columns whose header looks like money ($/price/cost/revenue) or percent (%) auto-format; the header row gets autofilter dropdowns; columns auto-fit. The first row of each sheet is the header (auto-styled bold/filled), body rows get zebra striping — you only supply values. Set outputFormat: "csv" for a plain CSV (first sheet only; no styling/formulas). EXAMPLE: sheets: [{ name: "Q2 Revenue", data: [["Month","Units","Price","Revenue"],["Apr",120,9.99,"=B2C2"],["Total","=SUM(B2:B2)","","=SUM(D2:D2)"]] }]. Sheet names MUST be specific (rejects 'Sheet1', 'Data', etc.). Use dryRun: true for preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags for registry search and discovery.
styleNoOptional fine-grained overrides merged on top of stylePreset.
titleNoWorkbook title (used for filename, registry, and auto-categorization).
dryRunNoReturn a preview without writing (default: false).
sheetsYesArray of sheet definitions. At least one is required. A cell string starting with '=' becomes a live formula (e.g. "=SUM(B2:B9)").
docTypeNoTone and depth of the documentation.
categoryNoDocument category for subfolder organization.
uploadUrlNoOPTIONAL. HTTPS URL of a receiver that will accept a JSON envelope `{data:base64, filename, mimeType, size}` POSTed with this Bearer auth. If you have NOT been given an uploadUrl in your context, OMIT this field and the tool just writes the file locally. Single-use semantics — do not retry on 4xx. Works with any compliant receiver (CogniRunner attachment-upload web trigger is the reference implementation, but the contract is generic).
clientHintNoHow the response should be shaped. 'interactive' = polished one-line message for end-users (no chatty registry/lineage notes). 'agent' = verbose response with all metadata for AI consumption. 'auto' (default) = detect from input shape or MCP_CLIENT_TYPE env var, falling back to 'agent'.
outputPathNoOptional. Default: derived from title.
descriptionNoBrief description stored in the registry.
stylePresetNoStyle preset. 'claude-like' (modern blue-accented professional) is the default for general-purpose docs. 'professional' is the executive serif look. Auto-selected from category if omitted.
outputFormatNo'xlsx' (default — full styling, formulas, autofilter) or 'csv' (plain text, first sheet only).
uploadFilenameNoOPTIONAL. Filename to put in the upload envelope. Defaults to the local file's basename. Useful when the local file got auto-suffixed (e.g. duplicate prevention) and you want a clean name on the receiver side.
uploadAuthHeaderNoOPTIONAL. Authorization header value for uploadUrl (e.g. 'Bearer abc123'). REQUIRED when uploadUrl is set; ignored otherwise. Never logged.
enforceDocsFolderNoIf false, allow output outside docs/. Default: true.
preventDuplicatesNoIf false, allow same-name duplicates. Default: true.
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral transparency. It extensively details behaviors: auto-formatting of money/percent columns, live formulas via '=', autofilter on headers, zebra striping, sheet name validation (rejects generic names), dry run for preview, upload URL semantics with single-use and non-retry advice, and default behavior for outputFormat. No contradictions exist, and the coverage is thorough.

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 detailed and includes an embedded example, which adds value but also length. It is well-structured with bold key terms and bullet-like exposition. While it could be slightly more concise, every sentence serves a purpose, and the front-loaded summary ('Create a styled Excel XLSX (or CSV).') immediately conveys the core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 17 parameters, only one required, and no output schema, the description covers all critical aspects: core operation, superpowers, sheet constraints, upload mechanics, style options, dry run, and filing defaults. It leaves no obvious gaps for an agent to misunderstand how to select or invoke the tool.

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?

Although schema description coverage is 100%, the description goes far beyond the schema by explaining how the data parameter works (first row as header, '=' for formulas), how style presets are auto-selected, the effect of dryRun, and the uploadUrl contract (single-use, generic receiver). It adds significant operational context that the schema alone cannot provide.

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 opens with a clear verb and resource: 'Create a styled Excel XLSX (or CSV).' It explicitly states the tool is for tabular and numeric data, listing concrete examples (budgets, trackers, KPIs). It also distinguishes from sibling tools by asserting that tabular content belongs here rather than in a doc, effectively differentiating itself from 'create-doc' and similar tools.

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?

The description provides clear when-to-use guidance: 'USE for ANY tabular/numeric data' with examples. It also gives a specific negative example: 'even a table inside a report belongs here, not in a doc.' However, it does not explicitly state when NOT to use the tool or mention alternative tools beyond the doc reference. A clear exclusion statement would elevate this to a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leanzero-srl/leanzero-mcp-doc-processor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server