Skip to main content
Glama
Sign In

signaltender-mcp

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

Generate GovCon Sources Sought, RFI & FAR 19.502-2 Set-Aside Shaping Response

generate_sources_sought_response
Read-onlyIdempotent

Analyze agency Sources Sought notices, Market Research RFIs, and Draft PWS/SOWs against a vendor's socioeconomic status (8(a), SDVOSB, HUBZone, WOSB/EDWOSB, Small Business) and past performance to generate a persuasive FAR 19.502-2 Rule-of-Two set-aside justification, a 13 CFR 121.402 NAICS & SBA size standard shaping analysis, a requirement-by-requirement capability alignment matrix, Contracting Officer / OSDBU acquisition-shaping recommendations, and a ready-to-submit Sources Sought / RFI response narrative. This is a read-only, stateless, non-destructive capture shaping generator (requires X-RapidAPI-Key; sources_sought_or_rfi_notice_text accepts 20 to 45,000 characters and vendor_capability_and_socioeconomic_profile accepts 20 to 35,000 characters). Use this tool during pre-RFP Market Research / Sources Sought / RFI phases to persuade the Contracting Officer to set aside an upcoming procurement for small business; use match_capability_statement instead for Gate-1 Bid/No-Bid Pwin scoring on an already-released RFP, or generate_rfp_response to draft final RFP proposal volumes. Use this tool when responding to pre-RFP Sources Sought notices or RFIs to lock in small-business set-asides under the FAR 19.502-2 Rule of Two; use match_capability_statement instead for full RFP Bid/No-Bid Pwin scoring, or generate_rfp_response for full proposal narrative drafting.

Input Schema

NameRequiredDescriptionDefault
target_set_aside_preferenceNoPreferred FAR Part 19 set-aside pathway to justify to the Contracting Officer and OSDBU ('8a_Sole_Source_or_Competitive', 'SDVOSB_Set_Aside', 'HUBZone_Set_Aside', 'WOSB_EDWOSB_Set_Aside', 'Total_Small_Business_Rule_of_Two', or 'Auto_Recommend').Auto_Recommend
sources_sought_or_rfi_notice_textYesFull text of the agency Sources Sought notice, Market Research RFI, SSN capability questions, or Draft PWS/SOW (20 to 45,000 characters).
vendor_capability_and_socioeconomic_profileYesVendor socioeconomic designations (8(a), SDVOSB, HUBZone, WOSB/EDWOSB, Small Business), UEI/CAGE, GSA MAS / GWAC contract vehicles, facility clearances, and past performance (20 to 35,000 characters).

Output Schema

NameRequiredDescriptionDefault
set_aside_shaping_confidence_scoreNo0-100 score indicating the strength of the vendor's case to persuade the Contracting Officer and OSDBU to set aside the procurement.
requirement_capability_alignment_matrixNoRequirement-by-requirement alignment table mapping agency RFI tasks to demonstrated prime capability and 13 CFR 125.6 workshare compliance.
rule_of_two_and_far_19_502_justificationNoFormal FAR 19.502-2 Rule-of-Two & FAR Part 10 market research justification proving two or more capable small businesses (or sole-source 8(a)/SDVOSB authority) exist at fair market prices.
naics_psc_and_size_standard_shaping_analysisNoAnalysis of the posted NAICS/PSC code under 13 CFR 121.402, recommending either retention or a higher/more accurate SBA size standard.
recommended_acquisition_strategy_and_set_asideNoRecommended acquisition vehicle (GSA MAS, 8(a) STARS III, VETS 2, Polaris, Open Market) and FAR Part 19 set-aside determination.
ready_to_submit_sources_sought_response_narrativeNoComplete, paste-ready Sources Sought / RFI Response Narrative (Corporate Overview, Socioeconomic & Vehicle Eligibility, Technical Capability, Past Performance, and Acquisition Strategy Recommendation).
contracting_officer_shaping_questions_and_recommendationsNoStrategic recommendations for the Contracting Officer and Small Business Specialist (OSDBU) to shape the final RFP in the vendor's favor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / contracting_officer_shaping_questions_and_recommendations / description
      Previous value: -"Strategic acquisition-shaping recommendations for the Contracting Officer and OSDBU."New value: +"Strategic recommendations for the Contracting Officer and Small Business Specialist (OSDBU) to shape the final RFP in the vendor's favor."
    • changedOutput schema / properties / naics_psc_and_size_standard_shaping_analysis / description
      Previous value: -"13 CFR 121.402 NAICS code and SBA size standard shaping analysis."New value: +"Analysis of the posted NAICS/PSC code under 13 CFR 121.402, recommending either retention or a higher/more accurate SBA size standard."
    • changedOutput schema / properties / ready_to_submit_sources_sought_response_narrative / description
      Previous value: -"Complete, paste-ready Sources Sought / RFI response narrative."New value: +"Complete, paste-ready Sources Sought / RFI Response Narrative (Corporate Overview, Socioeconomic & Vehicle Eligibility, Technical Capability, Past Performance, and Acquisition Strategy Recommendation)."
    • changedOutput schema / properties / recommended_acquisition_strategy_and_set_aside / description
      Previous value: -"Recommended contract vehicle (GSA MAS, 8(a) STARS III, VETS 2, Polaris, Open Market) and FAR Part 19 set-aside determination."New value: +"Recommended acquisition vehicle (GSA MAS, 8(a) STARS III, VETS 2, Polaris, Open Market) and FAR Part 19 set-aside determination."
    • changedOutput schema / properties / requirement_capability_alignment_matrix / description
      Previous value: -"Requirement-by-requirement alignment table mapping agency RFI tasks to prime capabilities and 13 CFR 125.6 compliance."New value: +"Requirement-by-requirement alignment table mapping agency RFI tasks to demonstrated prime capability and 13 CFR 125.6 workshare compliance."
    • changedOutput schema / properties / rule_of_two_and_far_19_502_justification / description
      Previous value: -"Formal FAR 19.502-2 Rule-of-Two and FAR Part 10 market research justification."New value: +"Formal FAR 19.502-2 Rule-of-Two & FAR Part 10 market research justification proving two or more capable small businesses (or sole-source 8(a)/SDVOSB authority) exist at fair market prices."
    • changedOutput schema / properties / set_aside_shaping_confidence_score / description
      Previous value: -"0-100 score indicating the strength of the vendor's Rule-of-Two / set-aside shaping case."New value: +"0-100 score indicating the strength of the vendor's case to persuade the Contracting Officer and OSDBU to set aside the procurement."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so restating 'read-only, stateless, non-destructive' adds no new information. The description does contribute real operational context not in the annotations: the X-RapidAPI-Key authentication requirement and the input length bounds (20–45,000 and 20–35,000 characters). It stops short of describing latency, output determinism across runs, or what happens on malformed notice text.

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 first sentence is a heavily loaded run-on bundling six deliverables, and the final sentence restates the usage routing (pre-RFP Sources Sought for FAR 19.502-2, vs. match_capability_statement and generate_rfp_response) almost verbatim from mid-paragraph. The redundant tail and the duplicated character limits inflate length without adding decision value, though the purpose is front-loaded.

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

Completeness4/5

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

Given an output schema exists, the description need not detail return values, and it still summarizes the deliverable set. Inputs are bounded, auth is disclosed, and the pre-RFP lifecycle position is clear, so an agent has everything needed to invoke correctly; only the conditional behavior of the enum parameter against the vendor profile is left unaddressed.

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%, including the set-aside enum values and the character limits, so the description's repetition of those same limits is redundant rather than additive. It does not explain how `target_set_aside_preference` interacts with the vendor's declared socioeconomic profile (e.g. whether an incompatible override is rejected or silently adjusted), which is the one parameter question an agent would actually have.

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 opening sentence names a specific verb (analyze/generate) and enumerates both the input artifact types (Sources Sought notices, Market Research RFIs, Draft PWS/SOWs) and the exact deliverables (FAR 19.502-2 Rule-of-Two justification, 13 CFR 121.402 NAICS/size-standard analysis, capability matrix, CO/OSDBU shaping recommendations, response narrative). This is far more specific than any sibling and instantly separates it from generic RFP-response tools.

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?

Explicit timing ('during pre-RFP Market Research / Sources Sought / RFI phases') plus named alternatives with the discriminating condition: `match_capability_statement` for Gate-1 Bid/No-Bid Pwin scoring on an already-released RFP, and `generate_rfp_response` for final proposal volumes. The when-not conditions are stated, not implied.

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