Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_autofilter

Destructive

Sets an autofilter on a worksheet range to enable filtering of tabular data, with optional dry-run and change tracking.

Instructions

Set worksheet autofilter for an explicit or inferred range.

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_autofilter"
  }
}

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.7/5.0
Behavior2/5

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

Annotations only supply destructiveHint=true; the description adds nothing about that risk. It does not say whether an existing autofilter is replaced, whether data is altered or just a view is set, or what dry_run and include_changes do behaviorally.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing details flagged 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 5-parameter mutation tool with no output schema and 80% undocumented schema coverage, one sentence is inadequate. An agent cannot tell what the tool changes, what dry_run returns, or how the inferred range is determined.

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 coverage is only 20% (filepath is the sole documented parameter). The description implies range_ref is optional by saying the range may be "inferred," but says nothing about sheet_name, dry_run, or include_changes, leaving most parameters undocumented in both places.

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 plus resource ("Set worksheet autofilter") and notes the range can be explicit or inferred, which tells an agent what the tool acts on. It does not distinguish itself from any sibling, but no sibling is an obvious near-duplicate here.

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 applying a filter through other means, no preconditions (does the sheet need data? must it be unprotected?), and no mention of dry_run as a safe preview path. The only hint is that the range may be inferred, which is usage-adjacent but not explicit.

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