SyncroMSP MCP Server

policies_create_folder

Create a new policy folder for a customer under an existing parent folder. Requires customer ID, folder name, and parent folder ID (retrieve via policies_list_folders).

Instructions

Create a new policy folder under an existing parent folder. customer_id, name, and parent_id are all required -- folders cannot be created at the root level (the root folder is auto-created per customer). Use policies_list_folders first to find the root or desired parent folder ID.

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": {
      "customer_id": "<customer_id>",
      "name": "<name>",
      "parent_id": "<parent_id>"
    },
    "name": "policies_create_folder"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Folder name (required)
`parent_id`	Yes	Parent policy folder ID (required) -- must belong to the same customer
`customer_id`	Yes	Customer ID this folder belongs to (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the root folder constraint and that parent_id must belong to the same customer (also in schema). However, it does not discuss error conditions, idempotency, or side effects, leaving gaps for an agent.

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

Conciseness5/5

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

Three sentences, efficiently front-loaded with the core purpose, no redundant information. Every sentence provides useful context.

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

Completeness4/5

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

For a creation tool with 3 required parameters and no output schema, the description covers prerequisites (use list_folders), constraints (no root creation), and parameter sourcing. Missing details on return value or success response, but otherwise 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?

Schema coverage is 100% with decent parameter descriptions. The description adds value by reinforcing required status, explaining the root folder constraint, and advising on how to obtain parent_id via policies_list_folders, which goes beyond the schema.

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

Purpose5/5

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

The description clearly states 'Create a new policy folder under an existing parent folder,' specifying the action, resource, and relationship. It distinguishes from siblings by mentioning root folder is auto-created and that folders cannot be created at root level, which is unique to folder creation.

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

Usage Guidelines5/5

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

Explicitly advises to use policies_list_folders first to find the root or desired parent folder ID, providing clear when-to-use and alternative guidance. Also notes that all three parameters are required and that folders cannot be created at root level.

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

Deploy Server