Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

diff_workbooks

Read-only

Compare two workbook files to identify structural changes and sampled cell-value differences, with optional inclusion and sampling controls for focused review.

Instructions

Diff two workbook files and report structural changes plus sampled cell-value changes.

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": {
      "before_filepath": "<before_filepath>",
      "after_filepath": "<after_filepath>"
    },
    "name": "diff_workbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sample_limitNo
after_filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
before_filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
include_cell_changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.0
    • addedInput schema / properties / after_filepath / description
      Added value: +"Reuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing."
    • addedInput schema / properties / before_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

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating operation. The description adds one genuine behavioral trait beyond annotations: cell-value changes are "sampled" rather than exhaustive, which explains why results may be partial. It does not state whether both workbooks must be open, what the sampling default is, or how the diff handles renamed/added sheets.

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?

A single front-loaded sentence with no filler; the resource and the two output categories appear immediately. Nothing is redundant with the title or annotations.

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

Completeness3/5

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

With no output schema, the description carries the burden of explaining return shape, yet it only broadly characterizes results as structural plus sampled value changes without saying how changes are grouped or reported. For a two-file comparison tool with 4 parameters, this is adequate but leaves an agent guessing about the result format.

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 50%: the two filepath parameters are documented (server-path conventions, absolute vs relative), but sample_limit and include_cell_changes have no schema descriptions at all. The description's word "sampled" hints at sample_limit's purpose but never explains what is counted, the default of 25, or what include_cell_changes=false suppresses, so the description fails to compensate for the coverage gap.

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 uses a specific verb ("Diff") with a clear resource ("two workbook files") and states the output categories ("structural changes plus sampled cell-value changes"). No sibling tool performs a file-to-file diff, so an agent can distinguish it from inspect_workbook_contract or explain_recipe_delta, though the description never names that distinction explicitly.

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?

There is no guidance on when to use this tool versus the many inspection siblings (inspect_workbook_contract, profile_workbook, audit_workbook), nor on prerequisites such as needing both files accessible server-side. The only usage context lives in the schema descriptions for the filepath parameters, not in the tool description.

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