Skip to main content
Glama
Sign In
smartsheet-mcp

smartsheet-mcp

by Kcrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

smartsheet_list_summary_fields

Retrieve paginated summary fields from a Smartsheet sheet. Control results with optional include and exclude flags.

Instructions

List a sheet's summary fields with pagination.

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_list_summary_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
excludeNoOptional exclude flags.
includeNoOptional include flags.
sheet_idYesSmartsheet sheet ID.
page_sizeNoResults per page.
include_allNoIf true, return all results (ignores page/page_size).

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?

With no annotations, the description must disclose behavioral traits. It only mentions pagination. It does not state that the operation is read-only, what permissions are needed, or the format of returned data. This is insufficient for a tool that likely returns a list of summary field objects.

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. It is concise but could benefit from a bit more detail without becoming verbose. The current structure is efficient.

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 number of parameters (6), no output schema, and sibling tools that might require differentiation, the description lacks completeness. It does not describe what is returned (e.g., field IDs, names, types), pagination defaults, or how it relates to other sheet summary tools.

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%, so the description adds no additional meaning beyond the parameter names and basic types. The mention of 'pagination' is already implied by page/page_size. Baseline of 3 is appropriate as the description provides no extra semantic value.

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 verb 'list' and the resource 'sheet's summary fields', and mentions pagination. It distinguishes from siblings like smartsheet_get_sheet_summary (which likely returns a summary object) and other list tools, though it could be more explicit about what 'summary fields' are.

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 (e.g., smartsheet_get_sheet_summary or other list tools). It does not specify prerequisites or exclusion criteria, relying solely on the generic 'list' verb.

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