Skip to main content
Glama
andrewkkchan

MCP Fivetran

by andrewkkchan

sync_connection

Trigger data synchronization for a Fivetran connection using its ID to update datasets and maintain current information.

Instructions

Tool for syncing a fivetran connection by ID.

Parameters:
    id (str): id of the connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'sync_connection' tool. It is decorated with @mcp.tool() for registration in FastMCP. The function unpauses the specified Fivetran connector and triggers a forced sync on the connection, returning the JSON response from the API.
    @mcp.tool()
    def sync_connection(id: str) -> str:
        """
        Tool for syncing a fivetran connection by ID.
    
        Parameters:
            id (str): id of the connection
        """
        url = f"https://api.fivetran.com/v1/connectors/{id}"
        data = {
            'paused': False
        }
    
        requests.request("PATCH", url, json=data, headers=headers)
    
        url = f"https://api.fivetran.com/v1/connections/{id}/sync"
        payload = {"force": True}
        response = requests.request("POST", url, json=payload, headers=headers)
    
        return response.json()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'syncs' a connection, implying a mutation or update action, but doesn't clarify whether this is a read-only operation, what syncing involves (e.g., data refresh, configuration update), potential side effects, or error conditions. This is a significant gap for a tool with implied mutation.

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 concise and front-loaded, with the purpose stated in the first sentence and parameter details following. There's no wasted text, but it could be more structured by explicitly separating purpose from parameters. Overall, it's efficient but slightly under-specified.

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 (a mutation tool with no annotations) and the presence of an output schema, the description is minimally adequate. It covers the basic purpose and parameter, but lacks behavioral details and usage context. The output schema may help, but the description doesn't reference it, leaving gaps in completeness.

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?

The description adds minimal semantics beyond the input schema, specifying that 'id' is the 'id of the connection'. With 0% schema description coverage, this provides some context, but it doesn't explain the format or source of the ID (e.g., from list_connections), leaving the agent with incomplete guidance. The baseline is 3 due to the single parameter being straightforward.

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

Purpose3/5

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

The description states the tool 'syncs a fivetran connection by ID', which provides a clear verb ('sync') and resource ('fivetran connection'). However, it doesn't differentiate from sibling tools like 'list_connections' or 'invite_fivetran_user', leaving the specific role of 'sync' somewhat vague without further context about what syncing entails.

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. The description lacks any mention of prerequisites, such as needing an existing connection ID, or context for when syncing is appropriate compared to listing connections or inviting users. This leaves the agent without direction on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrewkkchan/mcp_fivetran'

If you have feedback or need assistance with the MCP directory API, please join our Discord server