Skip to main content
Glama
Sign In

signaltender-mcp

by com.onrender.b2b-contract-parser-api
OverviewDiscussionsAdmin

Generate SBA Mentor-Protégé (13 CFR 125.9) & Joint Venture Operating Agreement

generate_mentor_protege_jv_agreement
Read-onlyIdempotent

Audit and generate SBA All-Small Mentor-Protégé Program Agreements (13 CFR 125.9) and unpopulated Joint Venture Operating Agreements (13 CFR 125.8, 121.103(h), 124.513 8(a), 126.616 HUBZone, 127.506 WOSB, 128.402 SDVOSB), returning an SBA affiliation safe-harbor overview, all mandatory 13 CFR 125.8(b)(2) Operating Agreement clauses (Protégé Managing Venturer & Responsible Manager controls neutralizing OHA negative-control protests, >= 40% substantive Protégé workshare, commensurate profit distribution, dual-signature JV bank account, and equipment/labor schedules), a quantitative 40% Protégé workshare and FAR 52.219-14 audit, and a 6-year SBA MPP Developmental Plan blueprint. This is a read-only, stateless, non-destructive GovCon corporate structuring and SBA compliance generator (requires X-RapidAPI-Key; mentor_and_protege_profile_text accepts 20 to 45,000 characters, while target_set_aside_and_jv_type and agreement_deliverable_scope calibrate SBA socio-economic JV rules and developmental assistance plans). Use this tool when drafting or auditing an SBA 13 CFR 125.8 Joint Venture Operating Agreement or 13 CFR 125.9 Mentor-Protégé Developmental Plan to survive OHA size/status protests; use generate_teaming_strategy instead for standard FAR Subpart 9.6 Prime/Subcontractor Teaming Agreements, or generate_small_business_participation for Large Business Prime FAR 52.219-9 Subcontracting Plans.

Input Schema

NameRequiredDescriptionDefault
agreement_deliverable_scopeNoDeliverable scope: 13 CFR 125.8(b)(2) Joint Venture Operating Agreement + Solicitation Addendum Clauses, 13 CFR 125.9 SBA Mentor-Protégé Developmental Plan, and OHA Size/Status Protest Pre-Audit (defaults to 'Full_13_CFR_125_8_JV_Operating_Agreement_Clauses_Plus_13_CFR_125_9_MPP_Developmental_Plan').Full_13_CFR_125_8_JV_Operating_Agreement_Clauses_Plus_13_CFR_125_9_MPP_Developmental_Plan
target_set_aside_and_jv_typeNoTarget socioeconomic set-aside and SBA JV regulation (13 CFR 125.8 Small Business, 128.402 SDVOSB, 124.513 8(a), 127.506 WOSB, or 126.616 HUBZone; defaults to 'Unpopulated_SDVOSB_And_All_Small_MPP_Joint_Venture_13_CFR_125_8_And_128_402').Unpopulated_SDVOSB_And_All_Small_MPP_Joint_Venture_13_CFR_125_8_And_128_402
mentor_and_protege_profile_textYesProfiles of the Protégé (Managing Venturer) and Mentor (Partner Venturer), socioeconomic certifications (Small, 8(a), SDVOSB, WOSB, HUBZone), target solicitation details, and proposed workshare split (20 to 45,000 characters).

Output Schema

NameRequiredDescriptionDefault
statusNoExecution status ('success').
mentor_protege_and_jv_overviewNoExecutive overview of SBA regulatory compliance, unpopulated LLC structure, affiliation safe harbor, and 2-year rule.
sba_mpp_developmental_plan_blueprintNoSBA All-Small Mentor-Protégé Program (13 CFR 125.9) developmental assistance blueprint and term compliance check.
thirteen_cfr_125_8_mandatory_clausesNoComplete set of 13 CFR 125.8(b)(2) mandatory Joint Venture Operating Agreement clauses neutralizing OHA protest traps.
forty_percent_workshare_and_limitations_auditNoQuantitative audit of FAR 52.219-14 Limitations on Subcontracting and the mandatory >= 40% Protégé workshare rule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint=true, and openWorldHint=false, and the description is consistent with them. Beyond annotations, it adds that the tool is stateless, requires X-RapidAPI-Key, returns a safe-harbor overview and compliance audit, and describes the character range for the profile input.

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 purpose and alternatives are front-loaded, but the description is a dense run-on with heavy parenthetical citations and a long clause list. Much of the regulatory detail is useful, yet the structure could be more scannable and less repetitive.

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, annotations, full schema descriptions, and an output schema, the description supplies enough context to invoke it correctly. It covers scope, preconditions, alternatives, and output components without omitting anything the agent needs.

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 all three parameters are already documented in the schema with defaults and length constraints. The description reinforces their roles, but mostly repeats schema information rather than adding new syntax or format guidance beyond what is already structured.

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 pairing: it audits and generates SBA Mentor-Protégé and Joint Venture Operating Agreements under named regulations. It explicitly distinguishes itself from sibling tools by naming generate_teaming_strategy and generate_small_business_participation as alternatives for different agreement types.

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 explicit when-to-use guidance: drafting or auditing an SBA 13 CFR 125.8 JV Operating Agreement or 13 CFR 125.9 MPP Development Plan to survive OHA protests. It also names two sibling alternatives and the conditions that select them, leaving little to inference.

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

All signaltender-mcp 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