Skip to main content
Glama
Sign In

SignalTender B2B, GovCon & LegalTech MCP Server

by io.github.aarbchen
OverviewDiscussionsAdmin

Generate GovCon 30/60/90-Day Phase-In / Phase-Out Transition & Incumbent Capture Plan

generate_phase_in_transition_plan
Read-onlyIdempotent

Generate a risk-mitigated 30/60/90-Day Phase-In and Phase-Out Transition Plan from solicitation Section C/L/M transition instructions and incumbent workforce context, returning a 0-100 Transition Risk Readiness Score, an executive transition summary, chronological Work Breakdown Structure (WBS) milestones across Days 1-30, 31-60, and 61-90 (plus Phase-Out), an Executive Order 14055 / Service Contract Act (SCA) Incumbent Workforce Capture & Right-of-First-Refusal retention plan with DD-254/DISS clearance crossover timelines and outreach scripts, functional Knowledge Transfer & Shadowing tracks with COR Operational Readiness Review (ORR) gates, a FAR 52.237-3 Continuity of Services Phase-Out checklist, and a ready-to-submit Shipley Transition Plan proposal volume. This is a read-only, stateless, non-destructive capture and program-management generator (requires X-RapidAPI-Key; solicitation_transition_and_sow_text accepts 30 to 75,000 characters, optional incumbent_workforce_and_clearance_context accepts up to 50,000 characters, and transition_timeline_window calibrates milestone cadences across 30-day rapid cutovers, standard 30/60/90-day transitions, 120-day enterprise transitions, and FAR 52.237-3 phase-outs). Use this tool when drafting a Phase-In / Phase-Out Transition Plan volume, WBS mobilization schedule, or incumbent staff capture strategy; use match_key_personnel instead to audit and format individual Key Personnel resumes and Letters of Commitment, or generate_teaming_strategy for 13 CFR 125.6 Prime/Sub workshare splits.

Input Schema

NameRequiredDescriptionDefault
target_agencyNoOptional issuing agency or contracting office.Department of Defense (DoD) / Federal & State Agency
clearance_requirementNoOptional personnel and facility security clearance level required (DD-254 / DISS / Public Trust).Secret / Top Secret SCI & Public Trust
transition_duration_daysNoOptional total Phase-In transition duration in calendar days (15 to 180; defaults to 90).
transition_timeline_windowNoTransition schedule profile ('Rapid_30_Day_Cutover', 'Standard_30_60_90_Day_Phase_In', 'Extended_120_Day_Enterprise_Transition', or 'Include_Phase_Out_FAR_52_237_3').Standard_30_60_90_Day_Phase_In
solicitation_transition_and_sow_textYesSolicitation Section C/L/M transition instructions, PWS scope, incumbent staffing size, clearance levels, and continuity-of-operations mandates (30 to 75,000 characters).
incumbent_workforce_and_clearance_contextNoOptional incumbent contractor details, target FTE count, Collective Bargaining Agreement (CBA) / Service Contract Act (SCA) context, and DD-254 facility/personnel security clearance transfer requirements (0 to 50,000 characters).

Output Schema

NameRequiredDescriptionDefault
statusNoExecution status ('success').
wbs_30_60_90_day_milestonesNoChronological Work Breakdown Structure (WBS) transition milestones across Days 1-30, Days 31-60, Days 61-90 (and Phase-Out) with activities, deliverables, exit criteria, and risk mitigations.
executive_transition_summaryNoExecutive summary of the zero-mission-disruption Phase-In / Phase-Out strategy, governance structure, and Day-1 Full Operational Capability (FOC) roadmap.
transition_risk_readiness_scoreNo0-100 score quantifying Day-1 operational continuity, incumbent capture probability, and FAR 52.237-3 compliance readiness.
ready_to_submit_transition_volumeNoComplete, paste-ready Shipley Phase-In / Phase-Out Transition Plan proposal volume narrative in Markdown.
incumbent_capture_and_retention_planNoComprehensive incumbent workforce capture, EO 14055 / SCA right-of-first-refusal compliance, DD-254/DISS clearance crossover timeline, and outreach script.
knowledge_transfer_and_shadowing_scheduleNoFunctional knowledge transfer tracks with side-by-side shadowing durations, artifact handover checklists, and COR Operational Readiness Review (ORR) gates.
far_52_237_3_phase_out_continuity_checklistNoFAR 52.237-3 Continuity of Services Phase-Out checklist covering GFE/GFP return, CUI sanitization, credential revocation, and successor contractor training.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / clearance_requirement
      Added value: +{
+  "default": "Secret / Top Secret SCI & Public Trust",
+  "description": "Optional personnel and facility security clearance level required (DD-254 / DISS / Public Trust).",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / target_agency
      Added value: +{
+  "default": "Department of Defense (DoD) / Federal & State Agency",
+  "description": "Optional issuing agency or contracting office.",
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / transition_duration_days
      Added value: +{
+  "default": 90,
+  "description": "Optional total Phase-In transition duration in calendar days (15 to 180; defaults to 90).",
+  "maximum": 180,
+  "minimum": 15,
+  "type": "integer"
+}
    • changedInput schema / properties / transition_timeline_window / description
      Previous value: -"Transition schedule profile ('Rapid_30_Day_Cutover', 'Standard_30_60_90_Day_Phase_In' [default], 'Extended_120_Day_Enterprise_Transition', or 'Include_Phase_Out_FAR_52_237_3')."New value: +"Transition schedule profile ('Rapid_30_Day_Cutover', 'Standard_30_60_90_Day_Phase_In', 'Extended_120_Day_Enterprise_Transition', or 'Include_Phase_Out_FAR_52_237_3')."
    • removedInput schema / properties / transition_timeline_window / enum
      Removed value: -[
-  "Rapid_30_Day_Cutover",
-  "Standard_30_60_90_Day_Phase_In",
-  "Extended_120_Day_Enterprise_Transition",
-  "Include_Phase_Out_FAR_52_237_3"
-]
    • changedOutput schema / properties / executive_transition_summary / description
      Previous value: -"Executive summary of the zero-mission-disruption Phase-In / Phase-Out strategy and Day-1 FOC roadmap."New value: +"Executive summary of the zero-mission-disruption Phase-In / Phase-Out strategy, governance structure, and Day-1 Full Operational Capability (FOC) roadmap."
    • changedOutput schema / properties / far_52_237_3_phase_out_continuity_checklist / description
      Previous value: -"FAR 52.237-3 Continuity of Services Phase-Out checklist items."New value: +"FAR 52.237-3 Continuity of Services Phase-Out checklist covering GFE/GFP return, CUI sanitization, credential revocation, and successor contractor training."
    • changedOutput schema / properties / incumbent_capture_and_retention_plan / description
      Previous value: -"Incumbent workforce capture plan with target retention %, EO 14055 / SCA right-of-first-refusal posture, DD-254/DISS clearance crossover timeline, and outreach script."New value: +"Comprehensive incumbent workforce capture, EO 14055 / SCA right-of-first-refusal compliance, DD-254/DISS clearance crossover timeline, and outreach script."
    • changedOutput schema / properties / wbs_30_60_90_day_milestones / description
      Previous value: -"Chronological WBS transition milestones across Days 1-30, 31-60, 61-90 (and Phase-Out) with activities, deliverables, exit criteria, and risk mitigations."New value: +"Chronological Work Breakdown Structure (WBS) transition milestones across Days 1-30, Days 31-60, Days 61-90 (and Phase-Out) with activities, deliverables, exit criteria, and risk mitigations."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds useful behavioral context beyond annotations, notably that the tool is stateless and requires an X-RapidAPI-Key, while also restating some annotation-covered non-destructive traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and informative, but it is organized as very long, dense sentences with multiple embedded lists. It also repeats schema-covered constraints such as character limits and annotation-covered read-only/non-destructive traits, reducing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the 100% schema coverage, the presence of an output schema, and the rich annotations, the description is complete enough for an agent to understand purpose, usage, constraints, authentication needs, and sibling alternatives. No critical invocation information appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter already has structured documentation. The description reinforces character limits and timeline calibration profiles, but largely repeats what the schema already provides rather than adding substantially new parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: generating a 30/60/90-day Phase-In/Phase-Out Transition Plan from solicitation and incumbent context. It also enumerates the key outputs, making the tool distinguishable from siblings that handle personnel resumes, teaming strategy, or compliance matrices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool: drafting a Phase-In/Phase-Out Transition Plan volume, WBS mobilization schedule, or incumbent staff capture strategy. It also names alternatives with their distinct purposes: `match_key_personnel` for Key Personnel resumes and Letters of Commitment, and `generate_teaming_strategy` for 13 CFR 125.6 Prime/Sub workshare splits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SignalTender B2B, GovCon & LegalTech MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources