Lock in teaming team MCP tool
Operates in the cross-company GovTribe teaming network. 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 - Data type: Teaming interest data type
- Returns: Teaming interest MCP response
- Annotations: Not read only, destructive, not idempotent, open world
- Available in: 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.
- Teaming interest data type: Understand the shared record fields and relationships used by this tool.
Load search results
Provides metadata and blob hydration not relevant to the context window
Read account
Read your account plan, AI/MCP prerequisites, available prepaid/promotional/included credits, your personal allowance, and PAYG spending headroom. Free to call, including after credit depletion or paid-usage suspension. Takes no arguments. Check before starting batches and use your own replenishment thresholds. Credits and USD headroom are separate; uncapped PAYG is not infinite credits. This is an advisory local snapshot, not authorization or reserved capacity. Unknown fields are not zero. Individual tools still enforce scopes, resource permissions and feature access.