Skip to main content
Glama
scmdr

SourceSync.ai MCP Server

by scmdr

updateConnection

Modify a data source connection to change sources, update redirect URLs, or select different documents for ingestion in SourceSync.ai's knowledge management platform.

Instructions

Updates a connection to a specific source. The connector parameter should be a valid SourceSync connector enum value. The clientRedirectUrl parameter is optional and can be used to specify a custom redirect URL for the connection. This will give you a authorization url which you can redirect the user to. The user will then be asked to pick the documents they want to ingest. This is useful if you want to update the connection to a different source or if you want to update the clientRedirectUrl or if you want to pick a different or new set of documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceIdNo
connectionIdYes
nameNo
clientRedirectUrlNo
tenantIdNo

Implementation Reference

  • MCP tool handler function for 'updateConnection': extracts parameters, creates SourceSyncApiClient instance, and invokes its updateConnection method wrapped in safeApiCall.
    async (params) => {
      return safeApiCall(async () => {
        const { namespaceId, tenantId, connectionId, name, clientRedirectUrl } =
          params
    
        // Create a client with the provided API key
        const client = createClient({ namespaceId, tenantId })
    
        return await client.updateConnection({
          connectionId,
          name,
          clientRedirectUrl,
        })
      })
    },
  • src/index.ts:695-714 (registration)
    Registration of the 'updateConnection' MCP tool using server.tool(), including name, description, input schema, and handler function.
    server.tool(
      'updateConnection',
      'Updates a connection to a specific source. The connector parameter should be a valid SourceSync connector enum value. The clientRedirectUrl parameter is optional and can be used to specify a custom redirect URL for the connection. This will give you a authorization url which you can redirect the user to. The user will then be asked to pick the documents they want to ingest. This is useful if you want to update the connection to a different source or if you want to update the clientRedirectUrl or if you want to pick a different or new set of documents.',
      UpdateConnectionSchema.shape,
      async (params) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, connectionId, name, clientRedirectUrl } =
            params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.updateConnection({
            connectionId,
            name,
            clientRedirectUrl,
          })
        })
      },
    )
  • Zod schema (UpdateConnectionSchema) for input validation of the updateConnection tool parameters.
    export const UpdateConnectionSchema = z.object({
      namespaceId: namespaceIdSchema.optional(),
      connectionId: z.string(),
      name: z.string().optional(),
      clientRedirectUrl: z.string().optional(),
      tenantId: tenantIdSchema,
    })
  • Core helper method in SourceSyncApiClient that performs the HTTP PATCH request to the SourceSync API endpoint /v1/connections/{connectionId} to update the connection details.
    public async updateConnection({
      connectionId,
      name,
      clientRedirectUrl,
    }: Omit<SourceSyncUpdateConnectionRequest, 'namespaceId'> & {
      connectionId: string
    }): Promise<SourceSyncUpdateConnectionResponse> {
      return this.client
        .url(`/v1/connections/${connectionId}`)
        .json({
          namespaceId: this.namespaceId,
          name,
          clientRedirectUrl,
        } satisfies SourceSyncUpdateConnectionRequest)
        .patch()
        .json<SourceSyncUpdateConnectionResponse>()
    }
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 mentions that the tool generates an authorization URL for user redirection and document selection, which adds useful context about the interactive flow. However, it doesn't cover critical aspects like required permissions, whether the update is reversible, rate limits, or what happens to existing settings not mentioned. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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?

The description is moderately concise but could be more front-loaded. It starts with the core function, then details parameters and usage, but includes some redundancy (e.g., repeating 'if you want to update' scenarios). Most sentences earn their place, but it could be streamlined for better clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a 5-parameter mutation tool with no annotations and no output schema, the description is incomplete. It covers the basic purpose and some parameter details but misses behavioral traits, full parameter explanations, and output information. For a tool that involves user authorization and document selection, more context is needed to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 for all 5 parameters. It only explains 'connector' (as a SourceSync connector enum) and 'clientRedirectUrl' (optional, for custom redirect URL), mentioning that the latter gives an authorization URL. It ignores 'namespaceId', 'connectionId', 'name', and 'tenantId', leaving most parameters undocumented. The description adds some value but fails to adequately cover the parameter semantics.

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 'updates a connection to a specific source' and mentions updating to a different source, clientRedirectUrl, or document selection. It specifies the verb 'updates' and resource 'connection', but doesn't explicitly distinguish it from sibling tools like 'updateNamespace' or 'updateDocuments' beyond the connection focus.

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?

The description implies usage scenarios ('if you want to update the connection to a different source or if you want to update the clientRedirectUrl or if you want to pick a different or new set of documents'), but doesn't explicitly state when to use this versus alternatives like 'createConnection' or 'revokeConnection'. It provides context but lacks clear exclusions or comparisons.

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/scmdr/sourcesyncai-mcp'

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