Skip to main content
Glama
fivetran

Fivetran MCP Server

Official
by fivetran

modify_connection_schema_config

Update schema configuration for a Fivetran connection, controlling which schemas and tables are synced. Specify schema change handling to allow or restrict new objects.

Instructions

⚠️ WRITE OPERATION - Confirm with user before calling. Updates the schema config for an existing connection within your Fivetran account. > NOTE: For backward compatibility, the response may contain the 'enable_new_by_default' boolean field. It defines whether new schemas and tables discovered in the source are synced. The value is 'true' if you specify 'ALLOW_ALL' as a value of 'schema_change_handling'. In the future API versions, we may remove this field. > > The response contains all known schemas and tables. Also, it contains columns whose state has ever been set by the user. For more information, see also the Connection Schema config tutorial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schema_fileYesREQUIRED: You must first read the schema file at 'open-api-definitions/connections/modify_connection_schema_config.json', then provide this exact path here to confirm.
request_bodyYesJSON string containing the request body. Refer to the schema file for the expected structure.
connection_idYesThe unique identifier for the connection
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the write nature and backward-compatibility behavior but omits side effects, authentication requirements, or rate limits. Provides some response content but not comprehensive.

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

Conciseness3/5

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

Description is somewhat verbose with repeated backward-compatibility note and includes redundant sentences. Could be more streamlined while retaining key warnings.

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 tool with no output schema and moderate complexity, the description covers purpose, workflow hints, and response contents. Links to external tutorial enhance completeness. Slightly incomplete on behavioral details.

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%, baseline 3. Description adds value by explaining the schema_file prerequisite and request_body format, clarifying the workflow beyond the schema itself.

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?

Clearly states 'Updates the schema config for an existing connection' with a specific verb and resource. The 'WRITE OPERATION' warning and context about backward compatibility differentiate it from sibling tools like modify_connection or modify_connection_table_config.

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

Usage Guidelines3/5

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

Includes a user confirmation warning but does not explicitly compare with sibling tools or specify when not to use this tool. Lacks guidance on choosing between modify_connection_schema_config and other modify_* tools.

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/fivetran/fivetran-mcp'

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