Skip to main content
Glama

Search the SheetSense formula library

search_formula_library
Read-only

Searches 60 hand-checked worked examples of common spreadsheet tasks (lookups, SUMIFS, dates, text cleanup, arrays) and returns the formula with Excel, Google Sheets, SQL and pandas versions, pitfalls and a link. Use for 'how do I ...' spreadsheet questions.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the user wants to do, e.g. 'lookup with two conditions' or 'count unique values'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish a safe read-only, closed-world operation, so the description need not restate safety. It adds genuinely new behavioral context: the corpus is fixed at 60 hand-checked examples, and each hit returns multi-dialect formulas, pitfalls and an external link. It stops short of saying how many results come back or how they are ranked.

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?

Two sentences, no filler, and the front-loaded clause states scope and corpus size before the payoff. The domain list and return-content list are packed efficiently into the first sentence.

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 single-parameter, read-only lookup with no output schema, the description is nearly sufficient: it covers scope, coverage domains, and what a result contains. The remaining gap is result cardinality and ranking/fallback behavior when nothing matches, which an agent would want to know.

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?

With only one parameter and 100% schema description coverage (including concrete examples like 'lookup with two conditions'), the schema already carries the semantics. The description reinforces that queries should be phrased as task intents rather than formula syntax, but adds no format or length guidance beyond that, so baseline 3 applies.

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 names a specific verb and resource ("Searches 60 hand-checked worked examples of common spreadsheet tasks") and enumerates the covered domains (lookups, SUMIFS, dates, text cleanup, arrays) plus the return payload (formula in Excel/Sheets/SQL/pandas, pitfalls, link). It is clearly a search-over-curated-examples tool rather than a formula explainer, though it never names the sibling explain_formula to make the boundary explicit.

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

Usage Guidelines4/5

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

"Use for 'how do I ...' spreadsheet questions" gives a clear triggering context that an agent can match against user intent. There are no exclusions or explicit pointer to an alternative for non-"how do I" cases, which keeps it out of 5 territory.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources