Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set View

set_view
DestructiveIdempotent

Set Excel sheet view options in one call: freeze or split panes, gridlines, headings, zoom, active selection, and tab color. Unchanged settings persist, with auto-backup and atomic save.

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

A3.8/5.0
Behavior4/5

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

Adds valuable context beyond the annotations, which is notable for a destructiveHint=true tool: auto-backup to .ks4xl-backups, atomic verified save, refusal while open in Excel, unset-parameters-keep-values semantics, and exclusivity between freeze and split. Not a 5 because the verification-failure path and what allow_loss actually permits are left unstated.

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?

Dense and waste-free: every clause maps to a parameter or behavior, with the core purpose front-loaded. It is a single packed paragraph that would scan better as bullets, but there is no filler or redundancy to penalize.

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 destructive tool with no output schema, the description covers an unusual amount: formats, valid ranges, defaults, the safety net (backup + atomic save), and the Excel-lock constraint. The only notable omissions are the semantics of allow_loss and verify_com and the response/verification contract on failure, which an agent would need for advanced or error cases.

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?

With 0% schema coverage the description carries the full burden and largely delivers: freeze='B2' semantics with 'clear', split={x,y} in points and exclusive with freeze, zoom range 10–400, selection as A1 cell or range, tab_color as 6-digit hex or 'clear', and unset-means-unchanged defaults. However, allow_loss and verify_com are completely unexplained, which is a real gap at zero schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Set sheet-view state in one call') and then enumerates the exact scope: freeze, split, gridlines, headings, zoom, selection, and tab color. This makes the tool's boundary clearly inferable against siblings like format_cells or set_dimensions, though it never names a sibling explicitly.

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?

Usage context is implied through the enumeration of settable view aspects and the 'in one call' framing, and constraints are disclosed ('sheet defaults to the active sheet', 'Refuses while open in Excel'). However, there is no explicit when-to-use vs alternatives guidance or exclusions, so the agent must infer selection criteria from the parameter list.

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