Add to vector store MCP response
MCP tool response returned by the Add to vector store MCP tool.
- Returned by: Add to vector store MCP tool
- Response type: Structured status snapshot
Response Shape
The tool returns a text message plus the same vector-store attachment status as structured content.
| Field | Type | Notes |
|---|---|---|
status | string | Operation status. Values are in_progress, completed, or failed. |
message | string | Human-readable status message for the current snapshot. |
govtribe_vector_store_id | string | GovTribe vector store identifier. |
oai_vector_store_id | string | Hosted OpenAI vector store identifier. |
requested_file_count | integer | Number of files requested for vector-store attachment. |
completed_file_count | integer | Number of requested files attached to the vector store. |
pending_file_count | integer | Number of requested files still attaching or indexing. |
failed_file_count | integer | Number of requested files that failed attachment. |
completed_file_names | string array | File names already attached to the vector store. |
pending_file_names | string array | File names still pending. |
failed_file_names | string array | File names that failed attachment. |
skipped_file_names | string array | File names skipped by the tool before upload. |
hosted_tool_ready | boolean | Whether the hosted file_search tool can use the vector store now. |
retry_with_same_arguments | boolean | Whether the agent should call the same tool again later with identical arguments. |
next_actions | object array | Structured guidance for the next MCP call or workflow step. Each item includes action, tool, and reason. |
failure_reasons | object array | Detectable failure or skipped-file reasons with code, message, and retry_hint. Empty when no repair guidance is needed. |
Follow-up Behavior
When status is in_progress and retry_with_same_arguments is true, follow next_actions and call Add_To_Vector_Store again later with the same arguments to get a fresh status snapshot.
Do not call Search_Vector_Store while status is in_progress or hosted_tool_ready is false.
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.
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 arguments to refresh readiness."
}
],
"failure_reasons": []
}