Skip to main content
Glama
scmdr

SourceSync.ai MCP Server

by scmdr

getIngestJobRunStatus

Check the status of a submitted ingestion job to monitor progress and completion in SourceSync.ai's knowledge management platform.

Instructions

Checks the status of a previously submitted ingestion job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceIdNo
ingestJobRunIdYes
tenantIdNo

Implementation Reference

  • MCP tool handler for getIngestJobRunStatus: creates SourceSync client and calls its getIngestJobRunStatus method, wrapped in safeApiCall.
    server.tool(
      'getIngestJobRunStatus',
      'Checks the status of a previously submitted ingestion job.',
      IngestJobRunStatusSchema.shape,
      async (params) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, ingestJobRunId } = params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.getIngestJobRunStatus({
            ingestJobRunId,
          })
        })
      },
    )
  • src/index.ts:333-349 (registration)
    Registers the 'getIngestJobRunStatus' tool with McpServer using IngestJobRunStatusSchema for input validation.
    server.tool(
      'getIngestJobRunStatus',
      'Checks the status of a previously submitted ingestion job.',
      IngestJobRunStatusSchema.shape,
      async (params) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, ingestJobRunId } = params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.getIngestJobRunStatus({
            ingestJobRunId,
          })
        })
      },
    )
  • Zod schema for input parameters to the getIngestJobRunStatus tool: namespaceId (optional), ingestJobRunId (required), tenantId (optional).
    export const IngestJobRunStatusSchema = z.object({
      namespaceId: namespaceIdSchema.optional(),
      ingestJobRunId: z.string(),
      tenantId: tenantIdSchema,
    })
  • SourceSyncApiClient method implementing the API call to retrieve ingest job run status via GET /v1/ingest-job-runs/{ingestJobRunId}.
    public async getIngestJobRunStatus({
      ingestJobRunId,
    }: Omit<
      SourceSyncGetIngestJobRunStatusRequest,
      'namespaceId'
    >): Promise<SourceSyncGetIngestJobRunStatusResponse> {
      return this.client
        .url(`/v1/ingest-job-runs/${ingestJobRunId}`)
        .query({ namespaceId: this.namespaceId })
        .get()
        .json<SourceSyncGetIngestJobRunStatusResponse>()
    }
  • TypeScript type definitions for the request (ingestJobRunId) and response (SourceSyncApiResponse<SourceSyncIngestJobRun>) of getIngestJobRunStatus.
    export type SourceSyncGetIngestJobRunStatusRequest = {
      ingestJobRunId: string
    }
    
    export type SourceSyncGetIngestJobRunStatusResponse =
      SourceSyncApiResponse<SourceSyncIngestJobRun>
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. It mentions checking status, which implies a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what the status response includes. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with no wasted information.

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 (status checking with 3 parameters), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on parameters, return values, and behavioral context, making it insufficient for effective use.

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 doesn't add any meaning beyond the schema, failing to explain parameters like 'namespaceId', 'ingestJobRunId', or 'tenantId'. With 3 parameters and no schema descriptions, this is inadequate.

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 verb ('Checks') and resource ('status of a previously submitted ingestion job'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'getNamespace' or 'getConnection', which also retrieve status/information, so it misses full sibling distinction.

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 minimal guidance by implying usage after job submission ('previously submitted'), but it doesn't specify when to use this tool versus alternatives like checking job status through other means or tools. No explicit when-not or alternative recommendations are given.

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