GovTribe

Add to container MCP tool

Adds accessible GovTribe User Files, files from file-bearing entities, or a typed Search_* search_results_id to the hosted `shell` tool under /mnt/data. Provide items, search_results_id, or both. Existing same-workspace User Files do not need to be uploaded to the conversation first. Returns the current status snapshot quickly; if status is in_progress, call Add_To_Container again later with the same arguments.

Examples

Use this when the user needs file content or typed-search JSON available in the hosted shell at /mnt/data, especially for spreadsheet, chart, document, dataset-join, PDF, or attachment workflows. Provide items, search_results_id, or both.

Reason directly from a typed Search_* response when its returned rows already answer the question. Normal searches remain file-free. Pass search_results_id here only when shell code needs the search page as JSON.

This is a polling tool. Read status, hosted_tool_ready, retry_with_same_arguments, next_actions, and container_files from each response. When status is in_progress and retry_with_same_arguments is true, call Add_To_Container again later with the same arguments. Do not use the hosted shell files until status is completed and hosted_tool_ready is true.

Add an opportunity attachment package to the container

{
  "tool": "Search_Federal_Contract_Opportunities",
  "arguments": {
    "query": "cybersecurity operations support attachments",
    "search_mode": "semantic",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "government_files"
    ]
  }
}
{
  "tool": "Add_To_Container",
  "arguments": {
    "items": [
      {
        "govtribe_type": "federal_contract_opportunity",
        "govtribe_id": "<federal_contract_opportunity_govtribe_id>"
      }
    ]
  }
}

Retry the same container add while files are still processing

{
  "tool": "Add_To_Container",
  "arguments": {
    "items": [
      {
        "govtribe_type": "government_file",
        "govtribe_id": "<government_file_govtribe_id>"
      }
    ]
  }
}

Add a typed-search page as JSON

{
  "tool": "Add_To_Container",
  "arguments": {
    "search_results_id": "<search_results_id_from_a_typed_search>"
  }
}

GovTribe reruns the exact typed-search page against current data, preserves its fields, filters, operators, sort, aggregations, and original search_results_id, and caps rows at the original returned count.

Payload patterns

Use items for one to ten file-bearing records, optional search_results_id for one typed-search page, or both. At least one input is required. Passing an entity adds its attached files; passing a file adds only that file. An accessible same-workspace User File does not need to be uploaded to the current conversation first. Keep the same arguments when polling an in-progress operation. Once files are ready, use container_files.container_file_id with Show_Document, container_files.path_hint for hosted shell commands, and container_files.sandbox_uri_hint when a response needs a sandbox link.

Add several known files at once

{
  "tool": "Add_To_Container",
  "arguments": {
    "items": [
      {
        "govtribe_type": "government_file",
        "govtribe_id": "<technical_volume_file_govtribe_id>"
      },
      {
        "govtribe_type": "user_file",
        "govtribe_id": "<pricing_workbook_user_file_govtribe_id>"
      }
    ]
  }
}

Add search JSON and a workspace file together

{
  "tool": "Add_To_Container",
  "arguments": {
    "search_results_id": "<search_results_id>",
    "items": [
      {
        "govtribe_type": "user_file",
        "govtribe_id": "<user_file_govtribe_id>"
      }
    ]
  }
}