Lock in teaming team MCP tool
Lock in a finalized team for a PRIME teaming interest. Requires at least one accepted match on the prime. Withdraws every PENDING inbound match request on the prime (those subs are notified their request was withdrawn), transitions the prime to matched, opens the team-hub conversation, and notifies accepted subs. From the agent, the only way back is `Disband_Teaming_Team` (which has wide blast radius). Prime-only. Before calling, name the accepted sub partners + the count of pending requests that will be withdrawn to the user and obtain explicit confirmation.
- MCP tool name:
Lock_In_Teaming_Team - Returns: Teaming interest MCP response
- Annotations: Not read only, destructive, not idempotent, closed world
- Surfaces: GovTribe AI
Examples
Resolve the prime interest, its accepted partners, and its pending inbound requests first so the user can confirm exactly which pending requests will be withdrawn when the team locks in.
Lock in a prime team after confirming accepted partners
{
"tool": "Search_Teaming_Interests",
"arguments": {
"teaming_interest_statuses": ["open"],
"teaming_interest_intents": ["prime"],
"fields_to_return": [
"govtribe_id",
"name",
"teamable",
"match_state_for_viewer",
"pending_match_count"
]
}
}{
"tool": "Lock_In_Teaming_Team",
"arguments": {
"teaming_interest_id": "<prime_teaming_interest_govtribe_id>"
}
}The call fails with the error code not_prime when the interest is a sub interest and no_accepted_matches when the prime has no accepted match yet.
Related articles
- Teaming interest MCP response: Review the response shape returned by this tool.
- GovTribe AI: Review the GovTribe AI surface where this tool can be called.
- Source identifiers and record matching: Use GovTribe IDs and source identifiers when passing records between tools.