Skip to main content
Glama
Sign In
smartsheet-mcp

smartsheet-mcp

by Kcrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

smartsheet_list_groups

Retrieve all groups associated with your Smartsheet account. Supports pagination and returning complete results.

Instructions

List groups in the user's account.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
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?

No annotations provided, so description carries full burden. It does not disclose that the tool is read-only, nor does it mention pagination behavior (e.g., default page size, effect of include_all). The description is too sparse to convey behavioral traits.

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 with no unnecessary words. It is front-loaded with the action. However, it might be overly terse, sacrificing useful context for brevity.

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?

For a list tool with three parameters and no output schema, the description should mention pagination alternatives, return format, and that the tool is read-only. It lacks these details, making it incomplete for confident agent usage.

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 descriptions for all three parameters (page, page_size, include_all). The tool description adds no extra meaning beyond what the schema already provides. Baseline 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?

Description clearly states 'List groups' as the verb and resource, and distinguishes from the sibling 'smartsheet_get_group' which retrieves a single group. However, the scope 'in the user's account' is somewhat vague, not specifying whether these are all account groups or user's personal groups.

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 on when to use this tool vs alternatives. Sibling tools include many list operations (e.g., smartsheet_list_users, smartsheet_list_contacts), but the description provides no context for choosing this tool over others.

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