Polytomic MCP Server

update_bulk_sync_schemas

Modify which data tables are included in a bulk synchronization process by updating schema configurations for a specified sync ID.

Instructions

Update which schemas/tables are enabled for a bulk sync.

Args: id: The bulk sync ID schemas: JSON array of schema configurations

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>",
      "schemas": "<schemas>"
    },
    "name": "update_bulk_sync_schemas"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`schemas`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this is an update operation, implying mutation, but doesn't disclose permissions needed, whether changes are reversible, rate limits, or what the output contains. The description lacks critical context for safe and effective use.

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 in the first sentence. The 'Args:' section is clear but could be integrated more seamlessly. Overall, it's efficient with minimal waste.

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 the tool's complexity (mutation with 2 parameters), no annotations, and an output schema (which reduces need to describe returns), the description is partially complete. It covers the basic purpose and parameters but lacks usage guidelines, behavioral details, and deeper parameter semantics, making it adequate but with clear gaps.

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 0%, so the description must compensate. It adds basic meaning for both parameters ('id' as bulk sync ID, 'schemas' as JSON array of schema configurations), which helps beyond the bare schema. However, it doesn't detail the format of 'schemas' (e.g., structure, allowed values) or provide examples, leaving gaps in understanding.

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 action ('Update which schemas/tables are enabled') and the target resource ('for a bulk sync'), making the purpose understandable. It distinguishes this from siblings like 'update_bulk_sync' (which likely updates general settings) and 'get_bulk_sync_schemas' (which reads them), but doesn't explicitly contrast with all alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing bulk sync), exclusions, or specific scenarios where this update is appropriate compared to other update operations in the sibling list.

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