Skip to main content
Glama

smartsheet_list_sheet_discussions

Fetch all discussions from a specified Smartsheet sheet, supporting pagination and optional include flags for detailed results.

Instructions

List all discussions on a sheet.

Input Schema

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

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

With no annotations, the description carries full burden for behavioral disclosure. It only states it lists discussions but omits key traits: that pagination is supported (page, page_size), that it can return all results (include_all), that optional include flags exist, and that it requires a sheet_id. The agent gets no insight into response behavior or side effects.

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 sentence, very concise. However, its brevity sacrifices valuable context. A slightly longer description could improve clarity 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 5 parameters, no output schema, and no annotations, the description is too brief. It fails to mention pagination, filtering options, or response structure. The tool is moderately complex, and the description inadequately prepares the agent for proper invocation.

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% (all 5 parameters described). The description adds no extra meaning beyond what the schema already provides. Baseline score of 3 is appropriate since the schema is complete but the description doesn't enrich it.

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 'List all discussions on a sheet' clearly states the action (list) and resource (discussions on a sheet). It differentiates from sibling tools like 'smartsheet_get_discussion' (single discussion) and 'smartsheet_list_row_discussions' (discussions per row) by implying the scope is all discussions on the entire sheet, though not explicitly.

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 such as 'smartsheet_get_discussion' or 'smartsheet_list_row_discussions'. There is no mention of prerequisites, context, or criteria for choosing this tool.

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