Dutify

pm_get_workspace_context

Read-onlyIdempotent

Single-call workspace orientation: members, spaces (with folders, lists, per-list statuses/priorities/taskTypes/customFields), workspace-level taskTypes, relationshipTypes, tags. The biggest agent-onboarding tool — call it first when starting in a new workspace. Folders nest at any depth: every folder has its own lists and its sub-folders in folders (same shape), so walk folders recursively to find every list. Only what you can see is returned; anything visible inside a folder you can't see is listed under the nearest visible parent. Pass shallow=true to skip per-list statuses/priorities for a faster tree-only response. Each per-list custom field carries an isMandatory flag — fields with isMandatory=true MUST be supplied in customFields when creating/updating a task in that list, or the write is rejected with 400 VALIDATION_ERROR. API-key scope: workspaces:read.

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": "pm_get_workspace_context"
  }
}

Input Schema

Name	Required	Description
`space`	No	Narrow to one space by name (exact match)
`account`	No	Multi-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.
`shallow`	No	Skip per-list statuses/priorities (faster)
`workspace`	No	Workspace 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.
`includeTags`	No	Default true
`includeTaskTypes`	No	Default true
`includeCustomFields`	No	Default true
`includeRelationshipTypes`	No	Default true

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description explains recursive folder nesting, visibility-based filtering behavior, the effect of shallow=true, the mandatory customFields requirement with its 400 VALIDATION_ERROR consequence, and the required API-key scope. This is substantial behavioral context for an agent.

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 front-loaded with the primary orientation purpose and then layers in recursion, visibility, shallow mode, mandatory custom fields, and auth scope. It is dense but appropriately sized for a high-value onboarding tool, with only minor room for tighter structure.

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?

With no output schema, the description usefully explains the response shape: members, spaces, nested folders, lists, per-list metadata, workspace-level reference data, and visibility filtering. It also covers the key caveat for customFields writes and the required API-key scope, leaving an agent well prepared to call and interpret the tool.

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 description coverage is 100%, so the schema already documents the parameters well. The description reinforces shallow=true and explains the isMandatory flag's downstream write impact, but it does not add much parameter-level detail beyond the structured schema for most inputs.

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 states a specific verb-and-resource purpose: a single-call workspace orientation returning members, spaces, folders, lists, statuses, priorities, task types, custom fields, relationship types, and tags. It also distinguishes this onboarding tool from narrower sibling tools by explicitly positioning it as the first call for a new workspace.

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?

It gives clear when-to-use guidance: call this first when starting in a new workspace, and use shallow=true for a faster tree-only response. It does not explicitly name sibling alternatives such as list_spaces or pm_list_reference_data, but the onboarding context is strong and actionable.

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

All Dutify tools Inspect

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

Need Help?