Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

set_view

Set freeze panes, split panes, gridlines, headings, zoom, selection, and tab color for an Excel sheet in one call, preserving unset values and backing up automatically.

Instructions

Set sheet-view state in one call: freeze panes (freeze='B2' locks the rows above and columns left of it; 'clear' removes), split panes (split={x, y} positions in points, exclusive with freeze), gridlines and headings visibility, zoom (10 to 400 percent), the active selection (an A1 cell or range), and the sheet tab color (6-digit hex or 'clear'). Unset parameters keep their current values; sheet defaults to the active sheet. Auto-backup to .ks4xl-backups; atomic verified save. Refuses while open in Excel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
zoomNo
sheetNo
splitNo
backupNo
freezeNo
headingsNo
gridlinesNo
selectionNo
tab_colorNo
allow_lossNo
verify_comNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With only readOnlyHint:false in annotations, the description carries the full burden and succeeds. It discloses auto-backup behavior, atomic verified save, refusal while the workbook is open in Excel, defaulting logic, and precise semantics for freeze, split, zoom, and tab color. There is no contradiction 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-organized: purpose is front-loaded, and each clause adds necessary detail about parameter behavior, defaults, and side effects. No filler or redundant restating of the schema.

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 12-parameter mutating tool with no output schema, the description is remarkably complete: it covers the view-state semantics, default behavior, backup safety, atomic save, and the Excel-lock refusal. The only meaningful gaps are the undocumented allow_loss and verify_com parameters and the lack of explicit return/result information.

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 0%, so the description must compensate. It explains most parameters: freeze, split, gridlines, headings, zoom, selection, tab_color, and sheet defaults. However, path, allow_loss, and verify_com are not semantically explained, so it does not fully cover all 12 parameters.

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 specific verb-resource pair, 'Set sheet-view state in one call', and enumerates the exact aspects it controls: freeze, split, gridlines, headings, zoom, selection, and tab color. This clearly distinguishes it from siblings like get_grid_view or format_cells even without naming alternatives.

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 gives clear context for when to use the tool: a one-call batch for multiple view settings, with unset parameters keeping current values and sheet defaulting to the active sheet. It also notes the split/freeze exclusivity. It does not explicitly name alternative tools, but the context is sufficient for correct routing.

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