Skip to main content
Glama

Dutify

by ai.dutify.mcp
OverviewDiscussionsAdmin

pm_create_list

Create a task list inside a space (optionally inside a folder). Space and folder are identified by name. Omit folder to create the list directly under the space. Prefer setting icon and color on create when the list purpose is known. For icon, prefer a semantic emoji name first; use an icon identifier only when no emoji fits. List setup is not finished after this call: unless the user requested a bare list, reuse/add relevant custom fields with emoji/color header metadata, refresh pm_get_workspace_context, then use pm_list_views and pm_update_view to configure the auto-created primary view with explicit ordered columns and useful grouping/sorting. Verify the saved configuration before reporting completion. API-key scope: lists:write.

Input Schema

NameRequiredDescriptionDefault
iconNoOptional list icon. Prefer semantic emoji names first (rocket, fire, direct_hit, white_check_mark, pushpin, moneybag); use icon identifiers only when no emoji fits.
nameYesList name
colorNoOptional list color, usually a hex color
spaceYesSpace name
folderNoOptional folder name
accountNoMulti-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
workspaceNoWorkspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.
idempotencyKeyNoOptional. Pass a UUID to dedupe retries within a 5-minute window. The same key inside the window returns 409 DUPLICATE_REQUEST regardless of body — query by name/identifier to find what was created on the first attempt; never assume the second call failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that creation is incomplete on its own, requires a multi-step post-configuration and verification before reporting done, and names the required `lists:write` scope. It is also consistent with idempotentHint=false by relying on the documented idempotencyKey retry rule rather than claiming inherent idempotency.

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 essential action and placement rule are front-loaded in the first two sentences with no waste. The post-creation workflow sentence is a long multi-step run-on (custom fields, context refresh, view config, verification) that could be split for scannability, costing a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation with no output schema, the description covers everything an agent needs: placement, optional attributes, the mandatory follow-on workflow, verification, and the auth scope. Nothing material about calling it correctly is left undocumented.

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 the baseline is 3; the description still adds real value by prescribing emoji-first semantics for `icon` and the omit-folder behavior for `folder`. It does not add anything about `account`, `workspace`, or `idempotencyKey`, but those are already fully documented in the schema.

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?

States a specific verb and resource ("Create a task list") plus its exact placement scope ("inside a space, optionally inside a folder"), which is the key differentiator from pm_create_space and pm_create_folder. The parenthetical also clarifies the folder omission behavior, so an agent can distinguish it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly covers when to omit folder, when to set icon/color ("when the list purpose is known"), and the exact when-not condition for skipping the follow-up workflow ("unless the user requested a bare list"). It also names the alternative/follow-up tools (pm_get_workspace_context, pm_list_views, pm_update_view) and the order to call them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dutify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources