Add to vector store MCP response

• Returned by: Add to vector store MCP tool
• Response type: Structured status snapshot with a text status message

Response Shape

Successful status responses include two equivalent forms:

• A text status message, shown by all MCP clients.
• Structured content with the fields below, shown only by clients that expose structured tool results.

Use the structured fields when the client exposes them. If the client only displays a prose snapshot such as Vector store ... has ... completed, ... pending, ... failed, follow that text message for retry, ready-for-search, and failure guidance.

Authorization, access, validation, or metering failures can return an error response instead of the structured status fields below.

Follow-up Behavior

When the response says the operation is still in_progress, call Add_To_Vector_Store again later with the same source items and the returned govtribe_vector_store_id to get a fresh status snapshot. If the first call omitted govtribe_vector_store_id, add the returned ID on the follow-up call; otherwise some external MCP clients may create a new vector store instead of polling the one already returned.

For complete package analysis, do not rely on Search_Vector_Store while status is in_progress or hosted_tool_ready is false. If a client calls Search_Vector_Store early, the response can say the vector store is not ready yet. In some situations it may return chunks for files that are already searchable while other requested files are still pending; treat those results as partial until this response reports the package is complete.

When status is completed and hosted_tool_ready is true, follow next_actions and call Search_Vector_Store with the returned govtribe_vector_store_id. Use Search vector store MCP response to interpret the structured results, snippets, and readiness messages.

If skipped_file_names is not empty, the status applies only to files supported by vector-store retrieval. When skipped files are spreadsheet-like sources such as pricing schedules, workbooks, CSV/TSV files, CLIN tables, budget templates, or staffing matrices, use Add_To_Container and hosted shell extraction before making complete package-level claims.

When status is failed, inspect failure_reasons before retrying. The response can distinguish no supported files, unsupported file types, and upload or indexing failure when that information is available.

Example

{
  "status": "in_progress",
  "message": "1 of 2 files is attached to the vector store. 1 file is still being processed.",
  "govtribe_vector_store_id": "VECTOR_STORE_ID",
  "oai_vector_store_id": "OAI_VECTOR_STORE_ID",
  "requested_file_count": 2,
  "completed_file_count": 1,
  "pending_file_count": 1,
  "failed_file_count": 0,
  "completed_file_names": ["statement-of-work.pdf"],
  "pending_file_names": ["pricing-workbook.xlsx"],
  "failed_file_names": [],
  "skipped_file_names": [],
  "hosted_tool_ready": false,
  "retry_with_same_arguments": true,
  "next_actions": [
    {
      "action": "retry_same_arguments",
      "tool": "Add_To_Vector_Store",
      "reason": "The files are still uploading or indexing. Retry with the same source items and this govtribe_vector_store_id to refresh readiness."
    }
  ],
  "failure_reasons": []
}

Text-only clients may display the same snapshot as prose, such as Vector store VECTOR_STORE_ID has 2 requested supported file(s): 1 completed, 1 pending, 0 failed. Pending files: "pricing-workbook.xlsx". Files are still attaching or indexing. Call Add_To_Vector_Store again later with the same source items and this govtribe_vector_store_id to check status.