Skip to main content
Glama
dragosh29

Plannr MCP Server

by dragosh29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List tasks

list_tasks
Read-onlyIdempotent

Retrieve and filter Plannr CRM tasks by client, assignee, plan or case, priority, due date, status, and open-only to find items needing action.

Instructions

Tasks on the firm, filtered as GET /api/v1/task documents: by client, assignee, related plan or case, priority, due date range, open only, name or status. Each task has its status, priority, due date, what it relates to, who it is assigned to, its author and who completed it (include=author,completed_by). What a user sees depends on their Plannr role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTask name (filter[name])
sortNoSort field; prefix with - for descending. The API's default is created_at.
due_afterNoOnly tasks due after this date (filter[due_after])
open_onlyNotrue: leave out tasks in the Completed and Archived columns (filter[open_tasks])
due_beforeNoOnly tasks due before this date (filter[due_before])
prioritiesNofilter[priority]
client_uuidNoOnly tasks for this client (filter[client_uuid])
max_resultsNoMost records to return; lists are fetched 100 per request, up to 10 requests
status_uuidNoOnly tasks in this status (filter[status_uuid]); see list_task_statuses
related_typeNoOnly tasks on a plan or on a case (filter[taskable_type])
related_uuidNoOnly tasks on this plan or case (filter[taskable_uuid])
assigned_to_uuidsNoOnly tasks assigned to these accounts (filter[assigned_to_uuids])
include_contact_detailsNoInclude assignees' and authors' email addresses, and stop redacting emails, phone numbers and postcodes typed into task and client names. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), so the description adds context beyond them: role-based result visibility and the fact that relationship data requires include=author,completed_by. It still does not discuss pagination limits or rate behavior beyond what the schema states.

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?

Front-loaded with purpose and filters, but the middle sentence is a long enumeration of returned fields that reads as padding. Efficient overall, slightly dense.

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

Completeness4/5

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

There is no output schema, and the description compensates by listing the fields each task carries, plus the role-based visibility caveat. For a 13-parameter list tool with zero required params, this covers what an agent needs before calling.

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 all 13 parameters including filter mappings and defaults. The description's mention of include=author,completed_by is the only added semantic, so the baseline 3 applies.

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 ('Tasks on the firm') and enumerates the exact filter axes the tool exposes (client, assignee, related plan/case, priority, due date, open only, name, status). An agent can distinguish it from get_task (single task) and list_task_statuses without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied through the enumerated filters; there is no explicit 'use when' or 'use instead of get_task' guidance. The note that visibility depends on the user's Plannr role is context but not a when-to-use rule.

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

Deploy Server

Other Tools