Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_worksheet_visibility

Destructive

Change a worksheet's visibility to visible, hidden, or veryHidden in an .xlsx workbook, so AI agents can control which sheets users see.

Instructions

Set worksheet visibility to visible, hidden, or veryHidden.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filepath": "<filepath>",
      "sheet_name": "<sheet_name>",
      "visibility": "<visibility>"
    },
    "name": "set_worksheet_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
sheet_nameYes
visibilityYes
include_changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • addedInput schema / properties / filepath / description
      Added value: +"Reuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing."
  2. First observedv0.8.0

TDQS

C2.8/5.0
Behavior2/5

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

The destructiveHint annotation already flags this as a mutation, but the description adds no behavioral context. It does not explain what hidden or veryHidden means in practice, whether visible restores prior state, how protected workbooks behave, or what dry_run changes.

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 a single front-loaded sentence with no filler. It is efficiently structured, though its brevity contributes to the completeness gaps scored elsewhere.

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

Completeness2/5

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

For a destructive worksheet mutation with no output schema and weak parameter documentation, the description is too thin. It does not cover dry-run semantics, side effects, or the meaning of include_changes, leaving an agent without enough context for safe invocation.

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

Parameters2/5

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

The description clarifies the visibility values, which is useful because the schema defines no enum for that parameter. However, with 5 parameters and only 20% schema description coverage, it leaves sheet_name format, dry_run, and include_changes unexplained, so it does not compensate for the low 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?

The description gives a specific verb ('Set') and resource ('worksheet visibility'), and lists the allowed visibility states. It is distinguishable from siblings such as delete_worksheet or set_worksheet_protection, but it does not explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer from the tool name alone that this is the tool for changing visibility rather than deleting or protecting a sheet.

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