PlanfixMCP

by alexd73

Overview Schema Source Related Servers Discussions Admin

Python

Remote

task_filters

List available task filters in Planfix to apply saved search criteria and manage tasks efficiently.

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_filters"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	No
`filters`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations and a minimal description, there is no disclosure of behavior such as read-only nature, authentication needs, or response format. The description only states the resource, so the agent gains no insight into side effects or access requirements.

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 a single short phrase with no redundancy or fluff. It is appropriately brief for a simple list tool, but it is under-specified rather than richly concise, lacking a full sentence or explanatory structure.

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

Completeness3/5

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

Given the tool has no parameters, an output schema, and a straightforward list function, the description provides enough to understand the resource at a basic level. However, it misses practical context such as how filters are scoped, whether they are shared across projects, or how to interpret the output, making it minimally complete.

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?

The tool has zero parameters and the schema defines no properties, so the description correctly omits parameter details. The baseline for a 0-parameter tool is 4, and no additional semantic information is needed.

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 'Список фильтров задач' ('List of task filters') clearly identifies the resource (task filters) and the intent (list). It distinguishes from sibling tools like task_list (which lists tasks) and contact_filters (which filters contacts), though it lacks an explicit verb and does not elaborate on the filter types.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or refer to sibling tools such as contact_filters or task_list, leaving the agent without direction for selection.

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