Skip to main content
Glama

updateNamespace

Modify an existing namespace configuration in SourceSync.ai to update storage, embedding, and integration settings for content management.

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 registration and handler implementation for 'updateNamespace'. Creates a SourceSync client instance and delegates to its updateNamespace method, wrapped in error handling.
    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 the input parameters for the updateNamespace tool, including optional configs for storage, embedding, and connectors.
    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 method, which performs a PATCH request to /v1/namespaces/{namespaceId} with the provided config updates. This is the core API implementation called by the MCP handler.
    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 inferred from the updateNamespaceSchema for input validation.
    export type UpdateNamespaceParams = z.infer<typeof updateNamespaceSchema>
  • Type definitions for SourceSyncUpdateNamespaceRequest and Response 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't describe what happens during the update (e.g., whether it overwrites all configuration or merges partial updates, what permissions are required, if it's reversible, or potential side effects). For a complex mutation tool with 12 parameters, this leaves significant behavioral gaps.

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 gets straight to the point without unnecessary words. It's appropriately sized for a basic description, though it could benefit from being more informative given the tool's complexity. The structure is front-loaded with the core action.

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 high complexity (12 parameters, nested objects, no output schema, and no annotations), the description is severely inadequate. It doesn't explain the namespace concept, parameter purposes, update behavior, or expected outcomes. For a mutation tool with extensive configuration options, this leaves the agent with insufficient context to use it effectively.

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 have descriptions in the schema. The tool description only vaguely mentions 'configuration parameters' without explaining what any of them do (e.g., namespaceId, fileStorageConfig, embeddingModelConfig). This fails to compensate for the complete lack of schema documentation, leaving parameters semantically undefined.

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's somewhat vague about what a 'namespace' represents in this context and doesn't distinguish it from sibling tools like 'updateConnection' or 'updateDocuments.' The purpose is understandable but lacks specificity about the namespace concept.

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., that a namespace must already exist), when not to use it, or how it differs from similar tools like 'updateConnection' or 'createNamespace.' The agent receives no contextual usage information beyond the basic action.

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

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