PlanfixMCP

by alexd73

Overview Schema Source Related Servers Discussions Admin

Python

Remote

project_by_id

Retrieve project details by ID. Specify project number and optional fields to get specific information.

Instructions

Проект по номеру

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "project_by_id"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Number of project
`fields`	No	Fields returned - custom field identifiers, system field names, comma-delimited. <br>Possible for system fields: id, name, description, status, owner, parent, template, group, counterparty, startDate, endDate, hiddenForEmployees, hiddenForClients, overdue, isCloseToDeadline, hasEndDate, assignees, participants, auditors, clientManagers, isDeleted, sourceObjectId, sourceDataVersion
`sourceId`	No	Unique identifier of the third-party application or system.

Output Schema

Name	Required	Description	Default
`result`	No
`project`	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 provided, so the description must carry the full burden. It does not disclose whether the operation is read-only, what it returns, error behavior, or any side effects. The single noun phrase gives no behavioral context whatsoever.

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 this is under-specification rather than conciseness. It has no sentence structure and fails to convey the tool's purpose. The brevity does not earn its place because it contributes no useful information.

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 having an output schema, the description is incomplete because it does not explain what the tool actually does. For a simple retrieval-by-ID tool, a minimal but clear statement like 'Gets a project by its ID' is expected. The current description is insufficient for an agent to select or invoke the tool correctly.

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%, with clear parameter descriptions for id, fields, and sourceId. The description adds nothing beyond the schema, but the schema itself adequately documents parameters, warranting a baseline of 3.

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?

The description is 'Проект по номеру' ('Project by number'), which is essentially a restatement of the tool name 'project_by_id'. It lacks a verb or action, so it does not specify what the tool does (e.g., get, retrieve, fetch). It also fails to distinguish from sibling tools like project_list or create_project.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions. Sibling tools also lack differentiation, leaving the agent to guess based solely on the name.

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