PlanfixMCP

by alexd73

Overview Schema Source Related Servers Discussions Admin

Python

Remote

project_group_list

Retrieve a list of project groups from Planfix, with optional field selection to return only needed data.

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

Input Schema

Name	Required	Description	Default
`fields`	No	Fields returned - system field names, comma-delimited. <br>Possible for system fields: id, name

Output Schema

Name	Required	Description	Default
`groups`	No
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

D1.4/5.0

Behavior1/5

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

No annotations are present, so the description carries full burden. It discloses no behavioral traits—nothing about read-only nature, response format, pagination, or error conditions. The description is a label, not an explanation.

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 extremely short, but it is under-specification rather than effective conciseness. It has no structure or front-loaded core action, just a noun phrase that adds no value.

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

Completeness1/5

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

Despite an output schema being present, the description fails to indicate what the output contains or how it behaves. A tool with one optional param and no behavioral explanation is incomplete for an AI agent deciding to invoke it.

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 describes the 'fields' parameter with full coverage (100%), so the schema provides meaning. The tool description adds no param information, but the baseline of 3 applies due to high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description is 'Группы проектов' ('Project groups'), a noun phrase that merely restates the tool name. It lacks a verb and does not specify what the tool does (e.g., list, retrieve, manage).

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

Usage Guidelines1/5

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

No guidance on when to use this tool vs alternatives. Sibling tools like project_list and project_by_id exist, but no distinctions or usage context are provided.

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