Skip to main content
Glama

revokeConnection

Remove integration with an external service by revoking access for a specific connection in the SourceSync.ai knowledge management platform.

Instructions

Revokes access for a specific connection, removing the integration with the external service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceIdNo
connectionIdYes
tenantIdNo

Implementation Reference

  • src/index.ts:716-732 (registration)
    Registration of the MCP tool 'revokeConnection' including inline handler function that creates SourceSyncApiClient and calls its revokeConnection method
    server.tool(
      'revokeConnection',
      'Revokes access for a specific connection, removing the integration with the external service.',
      RevokeConnectionSchema.shape,
      async (params) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, connectionId } = params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.revokeConnection({
            connectionId,
          })
        })
      },
    )
  • Handler function for revokeConnection tool: extracts params, creates client using createClient helper, calls client.revokeConnection
    async (params) => {
      return safeApiCall(async () => {
        const { namespaceId, tenantId, connectionId } = params
    
        // Create a client with the provided API key
        const client = createClient({ namespaceId, tenantId })
    
        return await client.revokeConnection({
          connectionId,
        })
      })
    },
  • Zod input schema for revokeConnection tool parameters
    export const RevokeConnectionSchema = z.object({
      namespaceId: namespaceIdSchema.optional(),
      connectionId: z.string(),
      tenantId: tenantIdSchema,
    })
  • SourceSyncApiClient.revokeConnection: makes POST request to SourceSync API /v1/connections/{connectionId}/revoke with namespaceId
    public async revokeConnection({
      connectionId,
    }: Omit<SourceSyncRevokeConnectionRequest, 'namespaceId'> & {
      connectionId: string
    }): Promise<SourceSyncRevokeConnectionResponse> {
      return this.client
        .url(`/v1/connections/${connectionId}/revoke`)
        .json({
          namespaceId: this.namespaceId,
        } satisfies SourceSyncRevokeConnectionRequest)
        .post()
        .json<SourceSyncRevokeConnectionResponse>()
    }
  • TypeScript type definitions for SourceSyncRevokeConnectionRequest and Response used by the client method.
    export type SourceSyncRevokeConnectionRequest = {
      namespaceId: string
    }
    
    export type SourceSyncRevokeConnectionResponse = SourceSyncApiResponse<{
      connection: SourceSyncConnection
    }>
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool 'revokes access' and 'removes integration', which implies a destructive mutation, but doesn't disclose behavioral traits like whether this is reversible, what permissions are needed, what happens to associated data, or error conditions.

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?

Single sentence, front-loaded with the core action, zero waste. Every word earns its place by conveying the essential purpose without redundancy.

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?

For a destructive mutation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks details on parameters, behavioral implications, error handling, and what happens post-revocation, leaving significant gaps for an AI agent.

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. It mentions 'specific connection' which hints at the 'connectionId' parameter, but doesn't explain the purpose of 'namespaceId' or 'tenantId', leaving two of three parameters undocumented. This adds minimal value beyond the schema.

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 action ('revokes access') and target ('specific connection'), and distinguishes it from siblings like 'deleteConnection' by focusing on access revocation rather than deletion. However, it doesn't explicitly differentiate from all siblings like 'updateConnection' or 'getConnection'.

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?

No explicit guidance on when to use this tool versus alternatives like 'deleteConnection' or 'updateConnection'. The description implies usage for removing integrations but doesn't specify prerequisites, consequences, or when other tools might be more appropriate.

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