Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Find Cells

find_cells
Read-only

Find every cell matching a value or formula across a workbook, sheet, or range, returning each match's address. Supports exact, contains, or regex queries with pagination and total count.

Instructions

Search cell values and/or formulas across a workbook, sheet, or range and return EVERY match with its unambiguous address (the plural sibling of the single-target search location selector). match is exact, contains, or regex (timeout-guarded, so a pathological pattern refuses instead of hanging); look_in is values, formulas, or both; a formula cell's searchable value is its last cached one. Results page with limit and offset and report the total match count. Read-only; works while the file is open in Excel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
limitNo
matchNocontains
queryYes
sheetNo
offsetNo
look_inNovalues
locationNo
match_caseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv1.1.0
    • addedInput schema / properties / location / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / location / title
      Removed value: -"Location"
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses timeout-guarded regex, the last-cached-value behavior for formula cells, pagination with limit/offset and total match count, and that it works while the file is open in Excel. These are material behavioral details an agent cannot derive from annotations or schema.

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?

The description is dense but every clause adds information: scope, match modes, regex timeout, look_in values, cached formula behavior, pagination, and read-only/open-file compatibility. The most important purpose and distinguishing trait are front-loaded.

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

Completeness4/5

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

For a 9-parameter tool with no output schema, the description covers many behavioral essentials and return semantics, but it omits the expected shape of the result payload and the meaning of the location parameter. This is a meaningful gap, but the core calling pattern is still well specified.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate; it does explain match, look_in, limit, and offset semantics. However, it leaves location, match_case, sheet, query, and path to inference, and location is a non-trivial union of string/object/null that needs more guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (search) and resource (cell values/formulas), scopes the search to a workbook, sheet, or range, and emphasizes that it returns EVERY match with an unambiguous address. This clearly separates it from a single-target location selector, even though the sibling is not named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the plural-sibling contrast and the read-only note, but it does not explicitly say when to prefer this over alternatives like query_range or get_cells, nor does it give exclusions. The context is clear enough for an inferred use case, but explicit routing guidance is missing.

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