Skip to main content
Glama
Sign In
Fivetran MCP Server

Fivetran MCP Server

Official
by fivetran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

connector_sdk_read

Read-only

Read Fivetran Connector SDK packages: list available packages, fetch package details, or download a package by endpoint name. Use list_endpoints(category='connector-sdk') to find endpoints.

Instructions

Read operations on Fivetran connector sdk (3 endpoints: download_connector_sdk_package, get_connector_sdk_package, list_connector_sdk_packages). Pass the endpoint name in name. Call list_endpoints(category='connector-sdk') for the full list.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body — dict or JSON string. Required for POST/PATCH endpoints.
nameYesEndpoint name within this resource:action group (from list_endpoints).
queryNoQuery-string parameters.
path_paramsNoValues for path placeholders like {connectionId}, {groupId}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish the safe read profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the burden is lighter. The description adds real behavioral value by disclosing that this is a multi-endpoint dispatcher and naming the three operations, which tells the agent what capabilities actually live behind this single tool.

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 compact sentences with no filler; the scope and endpoint inventory come first, followed by the usage and discovery hints. Every clause earns its place.

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 dispatcher tool with no output schema, it covers endpoints, the required parameter source, and the discovery path. It does not describe what the calls return (e.g., whether download yields a package URL or file), a minor gap given the endpoint names are self-explanatory.

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 100%, so all four parameters are already documented, including the note that `name` comes from list_endpoints. The description reinforces the `name` semantics and adds the concrete discovery call, but this borders on usage guidance rather than adding new parameter meaning — baseline 3 applies.

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?

States a specific verb and resource (read operations on the Fivetran connector SDK) and enumerates the three endpoints it dispatches to, so the agent knows exactly what surface is covered. Combined with the resource-specific name, it is clearly distinguishable from the other '_read' siblings.

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

Usage Guidelines4/5

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

Explains the dispatch mechanism ('Pass the endpoint name in `name`') and routes the agent to the discovery alternative ('Call list_endpoints(category='connector-sdk') for the full list'). It lacks an explicit when-not-to-use statement, but the operational context is clear.

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

Deploy Server

Other Tools