Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_print_area

Destructive

Set or clear a worksheet's print area in an Excel workbook by specifying the sheet and optional range reference, so only chosen cells print.

Instructions

Set or clear worksheet print area.

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>"
    },
    "name": "set_print_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
range_refNo
sheet_nameYes
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.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, so the description's main job would be adding context such as what clearing removes, whether the action is reversible, or how dry_run behaves. It adds almost none of that, only noting the dual set/clear behavior. That duality is a real behavioral fact but it is left unexplained in terms of trigger or consequence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

One front-loaded sentence with no filler, so nothing is wasted. But the brevity comes from under-specification rather than tight editing; the definition is too thin for a five-parameter mutation tool.

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, five-parameter mutation with no output schema and a dry_run flag, the agent needs to know how a dry run reports its would-be changes and how ranges map to the print area. Neither is covered, so an agent must guess at the tool's real contract.

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?

Schema description coverage is only 20% (filepath alone is documented), so the description must carry the load for range_ref, sheet_name, dry_run, and include_changes — yet it names none of them. At best, 'or clear' faintly implies range_ref can be null to remove the print area, but that is never stated and the other four parameters get no semantic help.

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?

States a specific verb pair and resource: setting or clearing a worksheet's print area. An agent can tell what it mutates without opening the schema. It does not differentiate itself from neighbors such as set_print_titles, which is a similar-sounding sibling an agent could confuse it with.

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?

No guidance on when to use this versus set_print_titles or other layout tools, and no stated prerequisites. The set-versus-clear distinction is only implicit in the word 'or' — the description never says that omitting the range clears the print area.

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