PlanfixMCP

by alexd73

Overview Schema Source Related Servers Discussions Admin

Python

Remote

recurring_task_list

List recurring tasks from Planfix with pagination, custom field selection, and optional source ID filter.

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": "recurring_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, dateOfLastUpdate, duration, durationUnit, durationType, overdue, closeToDeadLine, notAcceptedInTime, inFavorites, isSummary, isSequential, assignees, participants, auditors, recurrence, isDeleted, files, sourceObjectId, sourceDataVersion
`offset`	No	Offset from beginning of list
`pageSize`	No	Size of requested list
`sourceId`	No	Unique identifier of the third-party application or system.

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.7/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavior. It only implies a read-only list operation without describing pagination, filtering, sorting, or return format. This is insufficient for an agent to anticipate tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short phrase, which is concise, but it is under-specified to the point of being merely a label. There is no structure or additional helpful information, so it fails to earn its place as a useful description.

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 having an output schema and well-documented parameters, the description provides no context about the tool's purpose in a workflow, differences from sibling tools, or expected behavior. The tool appears to be one of many list operations, and the description does not complete the picture.

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?

The input schema provides full descriptions for all 4 parameters, so baseline is 3. The description adds no additional parameter context, but the schema already documents fields, offset, pageSize, and sourceId effectively.

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 'Список периодических задач' clearly indicates a list operation targeting recurring tasks. It specifies a distinct resource (recurring tasks) that differentiates it from the sibling 'task_list', though it does not explicitly name an alternative.

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?

There is no guidance on when to use this tool versus alternatives like 'task_list' or 'contact_list'. The description provides no context for selection or exclusions.

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