# Search FCV Subcategories

`Search_FCV_Subcategories` returns federal contract vehicle subdivisions across GovTribe. This includes GSA MAS SINs and non-MAS groupings such as lots, pools, lanes, and similar scoped subcategories under a parent vehicle.

## When To Use

Typical questions this tool answers well:

* Which MAS SINs or vehicle lots match a requirement area, capability, or keyword?
* Which subcategories belong to a known parent federal contract vehicle?
* Which subcategories are associated with a specific vendor, IDV, or funding agency?
* Which lots or SIN-like subdivisions share a given ceiling range?

## Required Reading

1. [Search\_Mode\_And\_Query\_Guide](/user-guide/mcp/guides/search_mode_and_query_guide.md): Required before setting free-text query strings and choosing keyword vs semantic retrieval.

## Filters

* `fcv_subcategory_ids`: Include or exclude specific FCV subcategory GovTribe IDs.
* `federal_contract_vehicle_ids`: Filter to subcategories under one or more parent vehicles.
* `federal_contract_idv_ids`: Filter to subcategories linked to one or more federal contract IDVs.
* `vendor_ids`: Filter to subcategories held by one or more vendors.
* `funding_federal_agency_ids`: Filter to subcategories tied to one or more funding federal agencies.
* `shared_ceiling_range`: Filter by the subcategory shared ceiling using `min` and/or `max`.

## Output Contract

* Top-level keys:
  * `current_page`
  * `data`
  * `from`
  * `last_page`
  * `path`
  * `per_page`
  * `to`
  * `total`
  * `contains`
  * `search_results_id_can_generate_saved_search`
  * `search_results_id`
  * `view_search_results_url`
* Row keys:
  * `govtribe_id`
  * `govtribe_type`
  * `name`
  * `short_name`
  * `alternate_name`
  * `description`
  * `descriptions`
  * `shared_ceiling`
  * `updated_at`
  * `federal_contract_vehicle`
  * `awardees`
  * `federal_contract_idvs`
  * `funding_federal_agencies`
* `govtribe_url` is intentionally absent because GovTribe does not currently expose a public show page for FCV subcategories.
* Relationship retrieval map:
  * `federal_contract_vehicle`
    * `resource_type`: `federal_contract_vehicle`
    * `tool`: `Search_Federal_Contract_Vehicles`
    * `filter`: `federal_contract_vehicle_ids`
  * `awardees`
    * `resource_type`: `vendor`
    * `tool`: `Search_Vendors`
    * `filter`: `vendor_ids`
  * `federal_contract_idvs`
    * `resource_type`: `federal_contract_idv`
    * `tool`: `Search_Federal_Contract_IDVs`
    * `filter`: `federal_contract_idv_ids`
  * `funding_federal_agencies`
    * `resource_type`: `federal_agency`
    * `tool`: `Search_Federal_Agencies`
    * `filter`: `funding_federal_agency_ids`

## Usage Patterns

Pattern A: Find MAS SINs or lots by keyword. Tool: `Search_FCV_Subcategories`

```json
{
  "query": "cloud computing SIN",
  "search_mode": "semantic",
  "fields_to_return": [
    "govtribe_id",
    "name",
    "description"
  ],
  "page": 1,
  "per_page": 10
}
```

Pattern B: List all subcategories under a parent vehicle. Tool: `Search_FCV_Subcategories`

```json
{
  "federal_contract_vehicle_ids": [
    "<FEDERAL_CONTRACT_VEHICLE_ID>"
  ],
  "federal_contract_vehicle_ids_operator": "in",
  "fields_to_return": [
    "govtribe_id",
    "name",
    "shared_ceiling"
  ],
  "page": 1,
  "per_page": 50
}
```

Pattern C: Narrow to vendor-held lots or SINs within a ceiling band. Tool: `Search_FCV_Subcategories`

```json
{
  "vendor_ids": [
    "<VENDOR_ID>"
  ],
  "vendor_ids_operator": "in",
  "shared_ceiling_range": {
    "min": 25000000,
    "max": 100000000
  },
  "fields_to_return": [
    "govtribe_id",
    "name",
    "shared_ceiling",
    "awardees"
  ],
  "page": 1,
  "per_page": 25
}
```


---

# 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-fcv-subcategories.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.