Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

query_table

Read-only

Filter, project, sort, and limit worksheet or table data to return only the rows and columns needed for analysis.

Instructions

Filter, project, sort, and limit worksheet or table data. Filters support eq/neq/ne, comparisons, string matching, blank checks, and in/not_in with value or values.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
selectNo
filtersNo
sort_byNo
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
row_modeNoarrays
sort_descNo
header_rowNo
sheet_nameNo
table_nameNo
infer_schemaNo

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

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

readOnlyHint=true already covers the safety profile, so the bar is lower. The description adds genuine capability context by enumerating the supported filter operators, but it says nothing about how limit interacts with filters, what row_mode does to the result shape, or whether infer_schema changes typing behavior.

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?

Two tight sentences with the primary operations front-loaded and no filler. The second sentence is information-dense but stays on topic.

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 an 11-parameter tool with no output schema, the description omits too much: result shape (affected by row_mode), sheet_name/table_name exclusivity, header_row semantics, and the structure of filter objects. An agent can form an intent but not a reliably correct call.

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 9% (only filepath is documented), so the description must carry the other ten parameters and it does not. It clarifies the filter vocabulary but never gives the filter object structure (key/op/value), and row_mode, header_row, sheet_name vs table_name, sort_desc, and infer_schema are left entirely undefined in both schema and prose.

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?

Names a specific verb set (filter, project, sort, limit) and the resource (worksheet or table data), which is more precise than the sibling read_excel_table or read_data_from_excel. It never contrasts itself with those read/aggregate siblings, so an agent must guess whether query_table, read_excel_as_table, or aggregate_table is the right entry point.

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 when-to-use statement, no exclusions, and no mention of the obvious alternatives (read_excel_table, read_excel_as_table, search_in_sheet, aggregate_table) in a sibling list of 70+ tools. Usage is only implied by the verb list.

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