# Search Vector Store

`Search_Vector_Store` runs semantic chunk retrieval against an existing GovTribe vector store and returns a plain-text answer payload, not a paginated dataset envelope.

## Output Contract

* Top-level keys:
  * `text_response`: single formatted text block returned by the tool call.
  * `result_summary`: first line reports either `Found N result(s) for: "<query>"` or `No results found for: "<query>"`.
  * `additional_results_note`: optional trailing note when more matches are available beyond returned entries.
* Row keys:
  * `rank`
  * `filename`
  * `relevance_percent`
  * `attributes`
  * `content_chunks`
* Relationship retrieval map:
  * `attributes.govtribe_id` with file-model attributes for workspace files
    * `tool`: `Search_User_Files`
    * `filter`: `user_file_ids`
  * `attributes.govtribe_id` with file-model attributes for government files
    * `tool`: `Search_Government_Files`
    * `filter`: `government_file_ids`
  * `filename` when ID attributes are absent
    * `tool`: `Search_User_Files`
    * `filter`: `query`
    * `fallback`: If the corpus is government-file based, use `Search_Government_Files` with `query` on the same filename phrase.

## Usage Patterns

Pattern A: Focused requirement extraction from a known store. Tool: `Search_Vector_Store`

```json
{
  "govtribe_vector_store_id": "<VECTOR_STORE_ID>",
  "query": "List mandatory proposal deliverables and submission format requirements.",
  "max_num_results": 5,
  "rewrite_query": false
}
```

Pattern B: Concept-level discovery with query rewriting enabled. Tool: `Search_Vector_Store`

```json
{
  "govtribe_vector_store_id": "<VECTOR_STORE_ID>",
  "query": "Summarize cybersecurity incident response expectations and timelines.",
  "max_num_results": 8,
  "rewrite_query": false
}
```

Pattern C: Quick triage pass to verify relevant evidence exists before deeper follow-up. Tool: `Search_Vector_Store`

```json
{
  "govtribe_vector_store_id": "<VECTOR_STORE_ID>",
  "query": "What are the key staffing qualifications and certifications?",
  "max_num_results": 3
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.govtribe.com/user-guide/mcp/tools/search-vector-store.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.