Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_in_sheet

Read-only

Locate cells in an Excel worksheet that match a specified value, with optional exact matching and a result limit.

Instructions

Search for cells matching a value in a worksheet.

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

Input Schema

NameRequiredDescriptionDefault
exactNo
queryYes
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
sheet_nameYes
max_resultsNo

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?

readOnlyHint=true already tells the agent this is a safe read, so the description owes no safety disclosure. Beyond that it adds nothing: no indication of what matches look like (cell addresses vs values), case sensitivity, cost/limits on scanning, or what exact=false changes. The single sentence is essentially a restatement of the title.

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 short, front-loaded sentence with zero redundancy, but the brevity is under-specification rather than economy – it leaves obvious questions unanswered given a five-parameter 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?

With five parameters, four undocumented, and no output schema, the definition should at minimum explain matching mode and result shape. Instead, an agent cannot tell whether results are cell addresses, values, or ranges, nor how exact=false modifies matching.

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% – only filepath is documented. The query, sheet_name, exact (default true), and max_results (default 50) parameters have no schema descriptions, and the description does not compensate: it never explains matching semantics for exact, what max_results truncation means, or whether query is typed as string/number/regex.

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 (search) and resource (cells matching a value in a worksheet), so an agent knows exactly what the operation does. It does not, however, distinguish itself from nearby read-oriented siblings such as query_table, read_data_from_excel, or quick_read.

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 gives no signal about when to prefer this over the many other read/query siblings, nor any prerequisites or exclusions. An agent must infer usage purely from the name.

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