Skip to main content
Glama
SheetForge MCP

SheetForge MCP

by iHeldan

bulk_aggregate_workbooks

Read-only

Aggregate comparable worksheet or table data across multiple Excel workbooks, using filters, grouping, metrics, and sorting to analyze cross-file data in one result.

Instructions

Aggregate comparable worksheet or table data across multiple workbooks.

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": {
      "filepaths": "<filepaths>"
    },
    "name": "bulk_aggregate_workbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filtersNo
metricsNo
sort_byNo
group_byNo
row_modeNoarrays
filepathsYes
sort_descNo
header_rowNo
sheet_nameNo
table_nameNo
schema_modeNostrict
infer_schemaNo
source_sample_limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • addedInput schema / properties / filepaths / items / 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
Behavior3/5

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

The readOnlyHint annotation establishes that this is a safe read operation, and the description is consistent with that. However, beyond the annotation, the description adds only the scope 'across multiple workbooks' and does not explain output shape, schema handling, limits, or what happens with non-comparable data.

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?

The description is a single, front-loaded sentence with no filler. It is concise, though extremely sparse given the tool's complexity.

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

Completeness1/5

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

For a 14-parameter aggregation tool with no output schema and almost no annotation detail, the description is far too thin. An agent cannot reliably infer how to use schema_mode, infer_schema, filters, metrics, grouping, sorting, or row modes.

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

Parameters1/5

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

There are 14 parameters with 0% schema description coverage, so the description must compensate for parameter semantics. It explains none of them: filters, metrics, group_by, sort_by, row_mode, schema_mode, infer_schema, source_sample_limit, header_row, sheet_name, and table_name are all left undocumented.

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 states a specific verb and resource: aggregate comparable worksheet or table data across multiple workbooks. It is clear enough for an agent to grasp the core operation, but it does not distinguish this tool from siblings such as aggregate_table, union_tables, or cross_workbook_lookup.

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?

The description implies usage by mentioning multiple workbooks, but it gives no explicit when-to-use or when-not-to-use guidance. It also fails to name alternatives like aggregate_table, bulk_filter_workbooks, or query_table.

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