SignalTender B2B, GovCon & LegalTech MCP Server

Generate 13 CFR 125.6 (50% Rule) Teaming & Subcontracting Plan

generate_teaming_strategy

Read-onlyIdempotent

Generate a legally compliant GovCon Teaming Strategy, a 13 CFR 125.6 & FAR 52.219-14 (Limitations on Subcontracting / 50% Rule) Prime/Sub workshare split, Ostensible Subcontractor risk audit, partner archetypes, FAR Subpart 9.6 Teaming Agreement clauses, and a BD outreach email. This is a read-only, stateless compliance and strategy generator (requires X-RapidAPI-Key; set_aside_type enforces SBA workshare ceilings for 'sdvosb' [default], '8a', 'wosb_edwosb', 'hubzone', 'small_business', or 'full_and_open', while bidder_role tailors outputs for 'prime_seeking_subs' [default], 'sub_seeking_prime', or 'joint_venture_mentor_protege'). Use this tool when structuring Prime/Sub workshare splits or recruiting teaming partners to fill capability gaps; use match_capability_statement instead for an initial single-vendor Bid/No-Bid Pwin score.

Input Schema

Name	Required	Description	Default
`rfp_text`	Yes	Raw RFP scope, PWS task areas, contract ceiling, security clearance requirements, and FAR 52.219-14 / set-aside instructions.
`bidder_role`	No	Bidder's teaming posture: 'prime_seeking_subs' (default, allocates >=50% to Prime and defines sub gap archetypes), 'sub_seeking_prime' (positions bidder for 20-49% specialty workshare), or 'joint_venture_mentor_protege' (13 CFR 125.8 JV compliance).	prime_seeking_subs
`set_aside_type`	No	Solicitation set-aside designation ('sdvosb' [default], '8a', 'wosb_edwosb', 'hubzone', 'small_business', or 'full_and_open') used to enforce 13 CFR 125.6 similarly situated entity and 50% self-performance rules.	sdvosb
`bidder_capabilities`	Yes	Bidder's socioeconomic status, self-performed technical domains, clearance level, and past performance strengths.

Output Schema

Name	Required	Description
`solicitation_title`	No	Inferred solicitation title, agency, and set-aside designation.
`teaming_agreement_clauses`	No	Ready-to-paste FAR Subpart 9.6 Teaming Agreement clauses (Exhibit A Workshare, Exclusivity, Pass-Through Subcontract Conversion).
`executive_teaming_rationale`	No	Strategic Shipley capture rationale explaining how this teaming structure maximizes Pwin while maintaining strict SBA/FAR compliance.
`recommended_teaming_structure`	No	High-level recommended teaming architecture (e.g., 'SDVOSB Prime (58% Workshare) + 1 Similarly Situated SDVOSB Sub (22%) + 1 Large Business Niche Sub (20%)').
`partner_outreach_email_template`	No	Ready-to-send Business Development outreach email to recruit the target Prime or Subcontractor partner.
`limitations_on_subcontracting_audit`	No	Automated audit of the workshare split under 13 CFR § 125.6 and FAR 52.219-14 (50% Rule & Ostensible Subcontractor test).
`capability_gaps_and_partner_archetypes`	No	Itemized capability gaps identified in the RFP and the exact partner profiles needed to close them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 29, 2026

addedOutput schema / properties / capability_gaps_and_partner_archetypes

Added value: +{
+  "description": "Itemized capability gaps identified in the RFP and the exact partner profiles needed to close them.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / executive_teaming_rationale

Added value: +{
+  "description": "Strategic Shipley capture rationale explaining how this teaming structure maximizes Pwin while maintaining strict SBA/FAR compliance.",
+  "type": "string"
+}

addedOutput schema / properties / limitations_on_subcontracting_audit

Added value: +{
+  "description": "Automated audit of the workshare split under 13 CFR § 125.6 and FAR 52.219-14 (50% Rule & Ostensible Subcontractor test).",
+  "type": "object"
+}

removedOutput schema / properties / ostensible_subcontractor_risk

Removed value: -{
-  "description": "SBA 13 CFR 121.103(h)(3) affiliation risk assessment and mitigation steps.",
-  "type": "string"
-}

removedOutput schema / properties / partner_outreach_email

Removed value: -{
-  "description": "Tailored business development outreach email to recruit teaming partners.",
-  "type": "string"
-}

addedOutput schema / properties / partner_outreach_email_template

Added value: +{
+  "description": "Ready-to-send Business Development outreach email to recruit the target Prime or Subcontractor partner.",
+  "type": "string"
+}

removedOutput schema / properties / recommended_partner_archetypes

Removed value: -{
-  "description": "Ideal subcontractor or prime partner profiles to close capability gaps.",
-  "items": {
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / recommended_teaming_structure

Added value: +{
+  "description": "High-level recommended teaming architecture (e.g., 'SDVOSB Prime (58% Workshare) + 1 Similarly Situated SDVOSB Sub (22%) + 1 Large Business Niche Sub (20%)').",
+  "type": "string"
+}

addedOutput schema / properties / solicitation_title

Added value: +{
+  "description": "Inferred solicitation title, agency, and set-aside designation.",
+  "type": "string"
+}

changedOutput schema / properties / teaming_agreement_clauses / description

Previous value: -"Ready-to-paste FAR Subpart 9.6 Teaming Agreement exclusivity and workshare clauses."New value: +"Ready-to-paste FAR Subpart 9.6 Teaming Agreement clauses (Exhibit A Workshare, Exclusivity, Pass-Through Subcontract Conversion)."

changedOutput schema / properties / teaming_agreement_clauses / items / type
```
Previous value: -"string"New value: +"object"
```

removedOutput schema / properties / workshare_allocation

Removed value: -{
-  "description": "Compliant Prime vs. Subcontractor percentage split under 13 CFR 125.6.",
-  "type": "object"
-}

Changed9 schema fields changedOct 21, 2026

changedInput schema / properties / bidder_capabilities / description

Previous value: -"Bidder's socioeconomic status, clearances, past performance, and technical capabilities."New value: +"Bidder's socioeconomic status, self-performed technical domains, clearance level, and past performance strengths."

addedInput schema / properties / bidder_capabilities / maxLength
```
Added value: +100000
```
addedInput schema / properties / bidder_capabilities / minLength
```
Added value: +30
```

addedInput schema / properties / bidder_role / description

Added value: +"Bidder's teaming posture: 'prime_seeking_subs' (default, allocates >=50% to Prime and defines sub gap archetypes), 'sub_seeking_prime' (positions bidder for 20-49% specialty workshare), or 'joint_venture_mentor_protege' (13 CFR 125.8 JV compliance)."

changedInput schema / properties / rfp_text / description

Previous value: -"Raw text from the RFP, Statement of Work (SOW), or Section L/M evaluation criteria."New value: +"Raw RFP scope, PWS task areas, contract ceiling, security clearance requirements, and FAR 52.219-14 / set-aside instructions."

addedInput schema / properties / rfp_text / maxLength
```
Added value: +100000
```
addedInput schema / properties / rfp_text / minLength
```
Added value: +40
```

addedInput schema / properties / set_aside_type / description

Added value: +"Solicitation set-aside designation ('sdvosb' [default], '8a', 'wosb_edwosb', 'hubzone', 'small_business', or 'full_and_open') used to enforce 13 CFR 125.6 similarly situated entity and 50% self-performance rules."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "ostensible_subcontractor_risk": {
+      "description": "SBA 13 CFR 121.103(h)(3) affiliation risk assessment and mitigation steps.",
+      "type": "string"
+    },
+    "partner_outreach_email": {
+      "description": "Tailored business development outreach email to recruit teaming partners.",
+      "type": "string"
+    },
+    "recommended_partner_archetypes": {
+      "description": "Ideal subcontractor or prime partner profiles to close capability gaps.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "teaming_agreement_clauses": {
+      "description": "Ready-to-paste FAR Subpart 9.6 Teaming Agreement exclusivity and workshare clauses.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "workshare_allocation": {
+      "description": "Compliant Prime vs. Subcontractor percentage split under 13 CFR 125.6.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the tool is stateless and requires an X-RapidAPI-Key. It also explains how `set_aside_type` enforces SBA workshare ceilings and how `bidder_role` tailors the output, which adds useful behavioral context for invocation.

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

Conciseness4/5

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

The description is front-loaded with the core output and efficiently covers usage, authentication, and parameter behavior. It is somewhat dense, and the parenthetical restates enum values already present in the schema, but there is little wasted framing.

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 complex compliance domain, rich annotations, complete schema descriptions, and output schema, the description provides everything needed to select and invoke the tool correctly. It covers purpose, alternatives, auth needs, statefulness, and key parameter effects.

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 the schema already documents parameter meanings, enums, defaults, and constraints. The description reinforces the role of `set_aside_type` and `bidder_role` but largely repeats what the schema already provides, so it meets the baseline without adding substantial new semantic detail.

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 states a specific verb and resource: generate a GovCon teaming strategy with 13 CFR 125.6/FAR 52.219-14 workshare split, ostensible subcontractor audit, partner archetypes, FAR Subpart 9.6 clauses, and outreach email. It also explicitly distinguishes the tool from the sibling `match_capability_statement`, which handles initial single-vendor Bid/No-Bid scoring.

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 gives an explicit use case: structuring Prime/Sub workshare splits or recruiting teaming partners to fill capability gaps. It also names the alternative tool and the condition for using it instead, removing ambiguity about tool selection.

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 tools Inspect

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.