Polytomic MCP Server

create_bulk_sync

Set up automated bulk data synchronization (ELT) between source and destination connections in Polytomic, with configurable schedules and connection-specific settings.

Instructions

Create a new bulk sync (ELT) in Polytomic.

Args: name: Name for the bulk sync source_connection_id: Source connection ID dest_connection_id: Destination connection ID destination_configuration: JSON string with destination config (e.g. {"schema": "public"}) schedule: Optional JSON for schedule source_configuration: Optional JSON string with source-specific config

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": {
      "name": "<name>",
      "source_connection_id": "<source_connection_id>",
      "dest_connection_id": "<dest_connection_id>",
      "destination_configuration": "<destination_configuration>"
    },
    "name": "create_bulk_sync"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`source_connection_id`	Yes
`dest_connection_id`	Yes
`destination_configuration`	Yes
`schedule`	No
`source_configuration`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 18, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create a new bulk sync' which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether this is idempotent, what happens on failure, rate limits, or what the output contains. The description adds minimal context beyond the basic action.

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 appropriately sized and front-loaded with the core purpose first, followed by parameter explanations. Every sentence earns its place by clarifying parameter meanings. The structure is logical, though the parameter explanations could be slightly more concise.

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 this is a creation tool with 6 parameters, 0% schema coverage, no annotations, but with an output schema present, the description is moderately complete. It explains parameter semantics well but lacks behavioral context and usage guidelines. The output schema existence means return values don't need description, but other gaps remain for a mutation 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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all 6 parameters, explaining what each represents (e.g., 'Name for the bulk sync', 'JSON string with destination config') and indicating which are optional. This adds substantial value beyond the bare schema, though it doesn't provide format examples beyond the destination_configuration hint.

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 clearly states the tool creates a new bulk sync (ELT) in Polytomic, which is a specific verb (create) and resource (bulk sync/ELT). It distinguishes from siblings like 'create_sync' by specifying 'bulk sync', though it doesn't explicitly contrast with other creation tools like 'create_connection' or 'create_model'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose create_bulk_sync over create_sync, or prerequisites like needing existing connections. The context of sibling tools suggests multiple creation options, but the description offers no differentiation.

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