Skip to main content
Glama
prmbr42-bot

Smartsheet MCP Server

by prmbr42-bot

Search Within Sheet

smartsheet_search_sheet
Read-onlyIdempotent

Search for text within a Smartsheet sheet, including cell values, formulas, comments, and summary fields to locate matching rows and cells.

Instructions

Search for text within a specific Smartsheet sheet. Searches cell values, formulas, comments, and summary fields within one sheet.

Args:

  • sheet_id (number): Sheet ID to search within

  • query (string): Text to search for

Returns: Matching rows and cells within the sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
queryYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds context by specifying that it searches multiple document types (comments, formulas, etc.), which is not evident from annotations alone.

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 extremely concise (4 lines), front-loaded with the core purpose, and every sentence adds value. No redundant or vague language.

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 simple search tool with 2 parameters, good annotations, and no output schema, the description covers purpose, parameters, and return value. However, it lacks details like case sensitivity or substring matching, which would fully complete the behavioral picture.

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

Parameters4/5

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

Schema coverage is 0%, but the description lists both parameters with clear explanations: sheet_id is the ID to search within, query is the text to search for. This compensates for the lack of schema descriptions.

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 clearly states the tool searches for text within a specific Smartsheet sheet, distinguishes from sibling 'smartsheet_search' (which searches across all sheets), and specifies searchable fields (cell values, formulas, comments, summary fields).

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 for searching within one sheet but does not explicitly compare to alternatives or state when not to use it. For example, it does not mention that broader searches should use 'smartsheet_search' or specify prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prmbr42-bot/smartsheet-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server