Skip to main content
Glama

smartsheet_search

Search across all Smartsheet items you can access, using query strings and optional filters like scope or modification date.

Instructions

Search across all Smartsheet items the user can access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string.
scopesNoRestrict to specific scopes.
includeNoOptional include flags.
locationNoSet to 'personalWorkspace' to limit scope.
modified_sinceNo
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'Search across all Smartsheet items the user can access,' lacking details on authentication, rate limits, result limitations, or side effects. This is insufficient for safe and correct usage.

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?

The description is a single concise sentence that front-loads the core purpose. It is not verbose, but could be slightly more informative without losing conciseness.

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?

Given the complexity (5 parameters, no output schema, no annotations), the description is too minimal. An agent needs to know return format, pagination, and other behavioral details. The description does not provide sufficient context for the agent to use the tool correctly.

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 80%, meaning most parameters already have descriptions in the schema. The tool description adds no additional meaning beyond what the schema provides. Therefore, a baseline score of 3 is appropriate.

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 clearly states it is a search tool across all accessible Smartsheet items. The verb 'search' and resource 'Smartsheet items' are specific, and it distinguishes itself from the sibling 'smartsheet_search_in_sheet' which likely searches within a single sheet. However, 'items' is broad and could be more precise.

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?

No guidance is provided on when to use this tool versus alternatives such as 'smartsheet_search_in_sheet' or list tools. There is no mention of prerequisites, context, or exclusions, making it hard for an agent to decide correctly.

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/Kcrong/smartsheet-mcp'

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