Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

smartsuite_list_my_work

Read-only

List your assigned work across solutions, including comment mentions, checklist items, and records. Get summaries with totals, overdue counts, and breakdowns by type, priority, or solution.

Instructions

List the authenticated user's assigned work ("My Work") — comment mentions, assigned checklist items, and records assigned via people fields — for answering questions like "what's on my plate?", "how many open items are overdue?", or "what's assigned to me in this solution?". Returns a summary (totals, overdue count, breakdowns by item type / priority / solution) plus the items themselves (with a truncated text preview). Defaults to open items; set status:"resolved" for completed work (which also returns per-period counts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return (default 50). The summary always reflects the full filtered set.
periodNoOptional time bucket filter (most useful with status:resolved).
statusNoopen (default) = unresolved assigned items; resolved = completed items.
itemTypeNoFilter by item type
priorityNoFilter by priority value (e.g. "high")
solutionIdNoFilter to one solution ID
overdueOnlyNoOnly items with a due date in the past (open items)
applicationIdNoFilter to one application ID
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds details about the response (summary, items, truncated preview) and defaults. No contradictions. Additional context like overdue counts and breakdowns is provided.

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 two sentences, efficiently delivering purpose and key details. It is front-loaded with the main action and includes examples. Could be slightly more concise, but overall well-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 8 parameters, no required ones, and no output schema, the description covers the main points (defaults, summary, item types). However, it lacks details on response structure beyond summary and items, and some parameter interactions (e.g., period with resolved) could be clearer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented. The description adds value by noting the default behavior (open items, limit 50) and how summary reflects full filtered set, which is not in the schema. Some parameter details (like period with resolved) are only implied.

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 lists the authenticated user's assigned work, specifies item types (comment mentions, checklist items, records) and gives example questions. It uniquely identifies its purpose among sibling tools.

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 explains default behavior (open items) and how to get completed work (status:resolved). It provides example questions, giving context for use. However, it does not explicitly exclude cases or compare to alternative tools.

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/SmartSuiteFoundry/smartsuite-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server