smartsheet-mcp

by Kcrong

Overview Schema Source Related Servers Discussions Admin

Python

Remote

smartsheet_get_sheet

Retrieve a Smartsheet's complete data including columns, rows, and cells. Supports pagination for large sheets.

Instructions

Get a sheet's full contents (columns + rows + cells). Use pagination for large sheets.

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": {
      "sheet_id": "<sheet_id>"
    },
    "name": "smartsheet_get_sheet"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page number.
`level`	No	API response level (e.g. 2 for multi-contact).
`exclude`	No	Optional exclude flags.
`include`	No	Optional include flags.
`row_ids`	No	Only these row IDs.
`sheet_id`	Yes	Smartsheet sheet ID.
`page_size`	No	Results per page.
`column_ids`	No	Only these column IDs.
`row_numbers`	No	Only these row numbers (1-based).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 1, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior but omits details like rate limits, performance impacts, or empty sheet handling. The description is adequate but not thorough for a complex tool.

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 two sentences with no wasted words. The first sentence states purpose, the second gives a critical usage tip (pagination). Perfectly concise and structured.

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

Completeness3/5

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

Given the tool has 9 optional parameters and no output schema, the description provides a basic understanding but lacks detail on the response structure or how to combine filters. For a 'get' operation, it's adequate but could be more complete with output format hints.

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 coverage is 100% with clear descriptions for all 9 parameters. The description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate. The description's mention of 'full contents' doesn't enhance parameter understanding.

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 retrieves a sheet's full contents (columns, rows, cells) and distinguishes it from siblings like smartsheet_get_row (specific row) or smartsheet_list_sheets (sheet list only). The verb 'Get' combined with 'full contents' is precise.

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?

The description advises using pagination for large sheets, which is a key usage hint. However, it lacks explicit when-not-to-use guidance, such as alternatives for fetching specific rows (smartsheet_get_row) or filtering (smartsheet_search_in_sheet). Still, the hint is helpful.

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

Deploy Server