Skip to main content
Glama
scmdr

SourceSync.ai MCP Server

by scmdr

updateNamespace

Modify configuration settings for a namespace to adjust file storage, vector databases, embedding models, or data source integrations in SourceSync.ai's knowledge management system.

Instructions

Updates an existing namespace with the provided configuration parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceIdNo
fileStorageConfigNo
vectorStorageConfigNo
embeddingModelConfigNo
webScraperConfigNo
notionConfigNo
googleDriveConfigNo
dropboxConfigNo
onedriveConfigNo
boxConfigNo
sharepointConfigNo
tenantIdNo

Implementation Reference

  • MCP tool handler for 'updateNamespace': extracts params, creates SourceSync client, and delegates to client.updateNamespace wrapped in safeApiCall.
    server.tool(
      'updateNamespace',
      'Updates an existing namespace with the provided configuration parameters.',
      updateNamespaceSchema.shape,
      async (params: UpdateNamespaceParams) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, ...updateParams } = params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.updateNamespace(updateParams)
        })
      },
    )
  • src/index.ts:176-190 (registration)
    Registers the 'updateNamespace' tool in the MCP server with description, input schema, and handler function.
    server.tool(
      'updateNamespace',
      'Updates an existing namespace with the provided configuration parameters.',
      updateNamespaceSchema.shape,
      async (params: UpdateNamespaceParams) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, ...updateParams } = params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.updateNamespace(updateParams)
        })
      },
    )
  • Zod schema defining input parameters for the updateNamespace tool, including optional configs for storage, embedding, etc.
    export const updateNamespaceSchema = z.object({
      namespaceId: namespaceIdSchema,
      fileStorageConfig: fileStorageConfigSchema.optional(),
      vectorStorageConfig: vectorStorageConfigSchema.optional(),
      embeddingModelConfig: embeddingModelConfigSchema.optional(),
      webScraperConfig: webScraperConfigSchema.optional(),
      notionConfig: notionConfigSchema.optional(),
      googleDriveConfig: googleDriveConfigSchema.optional(),
      dropboxConfig: dropboxConfigSchema.optional(),
      onedriveConfig: onedriveConfigSchema.optional(),
      boxConfig: boxConfigSchema.optional(),
      sharepointConfig: sharepointConfigSchema.optional(),
      tenantId: tenantIdSchema,
    })
  • SourceSyncApiClient.updateNamespace: core implementation that performs PATCH request to API endpoint /v1/namespaces/{namespaceId} with partial config updates.
    public async updateNamespace({
      fileStorageConfig,
      vectorStorageConfig,
      embeddingModelConfig,
      webScraperConfig,
      notionConfig,
      googleDriveConfig,
      dropboxConfig,
      onedriveConfig,
      boxConfig,
      sharepointConfig,
    }: SourceSyncUpdateNamespaceRequest): Promise<SourceSyncUpdateNamespaceResponse> {
      return this.client
        .url(`/v1/namespaces/${this.namespaceId}`)
        .json({
          fileStorageConfig,
          vectorStorageConfig,
          embeddingModelConfig,
          webScraperConfig,
          notionConfig,
          googleDriveConfig,
          dropboxConfig,
          onedriveConfig,
          boxConfig,
          sharepointConfig,
        } satisfies SourceSyncUpdateNamespaceRequest)
        .patch()
        .json<SourceSyncUpdateNamespaceResponse>()
    }
  • TypeScript type definitions for SourceSyncUpdateNamespaceRequest (input) and Response (output) used by the client implementation.
    export type SourceSyncUpdateNamespaceRequest = {
      fileStorageConfig?: SourceSyncFileStorageConfig
      vectorStorageConfig?: SourceSyncVectorStorageConfig
      embeddingModelConfig?: SourceSyncEmbeddingModelConfig
      webScraperConfig?: SourceSyncWebScraperConfig
      notionConfig?: SourceSyncNotionConfig
      googleDriveConfig?: SourceSyncGoogleDriveConfig
      dropboxConfig?: SourceSyncDropboxConfig
      onedriveConfig?: SourceSyncOnedriveConfig
      boxConfig?: SourceSyncBoxConfig
      sharepointConfig?: SourceSyncSharepointConfig
    }
    
    export type SourceSyncUpdateNamespaceResponse =
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, rate limits, or error handling. For a complex mutation tool with 12 parameters, this is a significant gap in transparency.

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 a single, efficient sentence that is front-loaded with the core action. There's no wasted verbiage, making it appropriately concise for a basic statement of function.

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 tool's complexity (12 parameters, nested objects, no output schema, and no annotations), the description is inadequate. It doesn't explain the scope of updates, parameter interactions, or expected outcomes. For a mutation tool with rich configuration options, more detail is needed to guide effective use.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning none of the 12 parameters are documented in the schema. The description only mentions 'configuration parameters' generically, without explaining what these parameters are (e.g., fileStorageConfig, embeddingModelConfig) or their purposes. This fails to compensate for the lack of schema documentation.

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 'Updates an existing namespace with the provided configuration parameters,' which is a clear verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'updateConnection' or 'updateDocuments,' nor does it specify what aspects of a namespace can be updated beyond 'configuration parameters.' This makes the purpose somewhat vague in context.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing namespace), exclusions, or comparisons to siblings like 'createNamespace' or 'getNamespace.' This leaves the agent without context for 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/scmdr/sourcesyncai-mcp'

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