Skip to main content
Glama
Sign In
PlanfixMCP

PlanfixMCP

by alexd73
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

contact_filters

Fetch contact filters from Planfix to retrieve predefined filtering criteria for contacts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultNo
filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/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 of behavioral disclosure. It only states 'list' without any details about read-only nature, pagination, sorting, or what exactly the filters are or how they are returned.

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 brief but under-specified. It is a noun phrase rather than a structured sentence, offering no additional value beyond the tool name. This is more under-specification than genuine conciseness.

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 too minimal to understand the tool's function or context. It does not explain what contact filters are, what they are used for, or how they relate to other contact tools, making it inadequate even for a simple list tool.

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 input schema has 0 parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it does not attempt to do so, which is appropriate in this case.

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

Purpose2/5

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

The description 'Список фильтров контактов' translates to 'List of contact filters', which is essentially a direct restatement of the tool name. It lacks a clear verb and resource structure and does not differentiate from sibling tools like 'contact_list' or 'contact_by_id'.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions no context, prerequisites, or exclusions, and does not reference any sibling tools or use cases.

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

Deploy Server

Other Tools