PlanfixMCP

Overview Schema Source Related Servers Discussions Admin

task_list

Retrieve tasks from Planfix by applying complex filters, selecting fields, and controlling pagination. Get the task list you need with customizable criteria.

Instructions

Список задач по фильтру

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

Input Schema

Name	Required	Description
`fields`	No	Fields returned - custom field identifiers, system field names, comma-delimited. <br>Possible for system fields: id, name, description, priority, status, processId, resultChecking, type, assigner, parent, object, template, project, counterparty, dateTime, startDateTime, endDateTime, hasStartDate, hasEndDate, hasStartTime, hasEndTime, delayedTillDate, actualCompletionDate, dateOfLastUpdate, dateOfLastComment, duration, durationUnit, durationType, overdue, closeToDeadLine, notAcceptedInTime, inFavorites, isSummary, isSequential, assignees, participants, auditors, recurrence, isDeleted, files, sourceObjectId, sourceDataVersion
`offset`	No	Offset from beginning of list
`filters`	No
`filterId`	No	Id for task filter, get list by method '/task/filters'
`pageSize`	No	Size of requested list
`sourceId`	No	Unique identifier of the third-party application or system.
`runAsUserId`	No	The employee or contact number with prefix on whose behalf the request will be executed if the token owner is an administrator.

Output Schema

Name	Required	Description	Default
`tasks`	No
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states a list by filter without disclosing pagination, sorting, or that it returns a filtered list. It does not add behavioral context beyond the literal meaning.

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 short phrase, which is concise but may be under-specified. It communicates the core purpose but lacks a complete sentence structure, making it less informative than ideal.

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?

Despite a rich input schema with complex filters and pagination, the description is minimal. With no annotations and an output schema present, the tool still requires more contextual guidance on its behavior, such as pagination and filter usage, so completeness is low.

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 86%, so the schema already documents parameters like fields, offset, filters, etc. The description adds no parameter-specific meaning, and the baseline for high coverage is 3.

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 'Список задач по фильтру' translates to 'List of tasks by filter', which clearly identifies the tool as a task-listing endpoint supporting filters. It stands out from siblings like task_by_id or create_task, though it lacks an explicit verb like 'get' or 'retrieve'.

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?

The description provides no guidance on when to use this tool versus alternatives like task_by_id, create_task, or contact_list. There is no mention of use cases, exclusions, or comparisons with sibling tools.

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