Skip to main content
Glama
Sign In
smartsheet-mcp

smartsheet-mcp

by Kcrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

smartsheet_list_sheets

List all Smartsheet sheets you have access to, with pagination and optional date filter to find recently modified sheets.

Instructions

List sheets the authenticated user has access to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smartsheet_list_sheets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
page_sizeNoResults per page.
include_allNoIf true, return all results (ignores page/page_size).
modified_sinceNoISO-8601 timestamp filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as pagination behavior, whether deleted sheets are included, permissions needed, or response format. The single sentence 'List sheets the authenticated user has access to' is insufficient for a list tool with filtering parameters.

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, clear sentence with no wasted words. It is appropriately front-loaded. However, it could be slightly expanded to include behavioral context 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?

The tool has 4 parameters (paginated, filterable) and no output schema or annotations. The description does not explain return format (e.g., what fields are returned for each sheet) or how to use the parameters together. It is incomplete for a list tool of moderate complexity.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it does not explain parameter interplay (e.g., include_all overrides page/page_size) or provide usage examples. No value added over the schema.

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 the action (List) and resource (sheets) with a scope (authenticated user's access). It distinguishes from sibling tools that list other resources (e.g., workspaces, reports) by the resource name, though no explicit differentiation is provided.

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 provides no guidance on when to use this tool versus alternatives. With many sibling list tools, the description only states the basic function, missing contextual cues like 'use to enumerate available sheets before selecting one for operations.'

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