Skip to main content
Glama

smartsheet_list_automation_rules

List automation rules on a sheet to review and manage scheduled alerts, approvals, and automated workflows.

Instructions

List automation rules on a sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
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 and no output schema, the description fails to disclose behavioral traits like read-only nature, pagination behavior, or rate limits. The term 'list' implies it is a read operation, but this is not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it lacks necessary details for effective use, making it under-informative despite its 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?

Given 4 parameters and no output schema, the description is incomplete. It does not specify return format, pagination details, or behavior when no rules exist, limiting the agent's ability to use the tool correctly.

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?

The input schema has 100% coverage with descriptions for all 4 parameters. The description adds no additional meaning or context beyond the schema, achieving the baseline score.

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 'List automation rules on a sheet' with a specific verb and resource, but does not explicitly differentiate from the sibling 'smartsheet_get_automation_rule' tool or clarify if it returns all rules.

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 is provided on when to use this tool versus alternatives, such as 'smartsheet_get_automation_rule' for a single rule. There is no mention of prerequisites or context.

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