Skip to main content
Glama
Sign In

signaltender-mcp

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

GovCon M&A Contract Novation (FAR 42.1204) & Change-of-Name Due Diligence Package

generate_novated_merger_change_of_name_far_42
Read-onlyIdempotent

Generate a complete FAR 42.1204 Three-Party Novation Agreement package for GovCon asset/stock acquisitions, auditing anti-assignment exceptions (41 U.S.C. 6305), SAM.gov UEI/CAGE transfer checklists, and SBA recertification triggers under 13 CFR 121.404(g). Returns a strictly validated NovationFar42Response JSON object containing transaction_structure_and_novation_overview, far_42_1204_document_checklist_and_three_party_agreement, sba_13_cfr_121_404_recertification_and_backlog_audit, and sam_uei_cage_and_dcsa_fcl_transition_runbook grounded in 41 U.S.C. § 6305 (Anti-Assignment Act), FAR Subpart 42.12 (FAR 42.1204 Novation & FAR 42.1205 Change-of-Name), & 13 CFR § 121.404(g). This is a read-only, stateless, non-destructive GovCon compliance and capture analysis call (requires X-RapidAPI-Key or X-SignalTender-Key; m_and_a_transaction_and_contract_backlog_text accepts 15 to 45,000 characters, while deal_structure_and_pathway and small_business_and_clearance_context calibrate the regulatory regime and threshold assumptions). Use this tool when executing GovCon M&A Contract Novation (FAR 42.1204) & Change-of-Name Due Diligence Package workflows; use scan_far_dfars_clauses instead for general FAR/DFARS clause flow-down audits, or generate_compliance_matrix for general Section L/M 'shall' requirement extraction.

Input Schema

NameRequiredDescriptionDefault
deal_structure_and_pathwayNoTarget regulatory regime, statutory authority, or evaluation framework (defaults to 'Asset_Purchase_Requiring_FAR_42_1204_Three_Party_Novation_vs_Stock_Purchase_Or_FAR_42_1205_Change_Of_Name').Asset_Purchase_Requiring_FAR_42_1204_Three_Party_Novation_vs_Stock_Purchase_Or_FAR_42_1205_Change_Of_Name
small_business_and_clearance_contextNoOperational context, threshold parameters, or compliance posture assumptions (defaults to 'Audit 13 CFR 121.404(g) 30-Day SBA Size Recertification, GWAC/MAC Eligibility, & DCSA 32 CFR 117 Changed Condition Package').Audit 13 CFR 121.404(g) 30-Day SBA Size Recertification, GWAC/MAC Eligibility, & DCSA 32 CFR 117 Changed Condition Package
m_and_a_transaction_and_contract_backlog_textYesPrimary solicitation text, clause excerpts, deliverable schedule, or technical/financial context for GovCon M&A Contract Novation (FAR 42.1204) & Change-of-Name Due Diligence Package (15 to 45,000 characters).

Output Schema

NameRequiredDescriptionDefault
statusNoExecution status ('success').
transaction_structure_and_novation_overviewNoExecutive determination overview, regulatory citations, and readiness score.
sam_uei_cage_and_dcsa_fcl_transition_runbookNoStatutory governance protocol and actionable submission verification checklist.
sba_13_cfr_121_404_recertification_and_backlog_auditNoPaste-ready compliance narratives, control specifications, or submission sections.
far_42_1204_document_checklist_and_three_party_agreementNoStructured line-by-line regulatory audit, classification, or quantitative schedule rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description does not need to carry the full safety profile. It adds useful operational context beyond annotations: API key requirement, stateless behavior, strict validation, and input length limits for the primary text parameter.

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 is front-loaded and the description includes valuable routing and output-field details, but it is a dense single paragraph with redundancy against the title, schema, and annotations. It could be more scannable and would benefit from separating purpose, return shape, usage alternatives, and parameter roles.

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?

For a complex compliance-generation tool, the description supplies the legal framework, expected output object components, input size constraints, authentication requirement, safety profile, and sibling distinctions. With an output schema present and 100% parameter description coverage, 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 the schema already documents all three parameters. The description adds some framing by noting that the primary text accepts 15 to 45,000 characters and that the other parameters calibrate regulatory regime and threshold assumptions, but this largely mirrors schema descriptions rather than adding new syntax or interpretation guidance.

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-resource pairing: generating a FAR 42.1204 Three-Party Novation Agreement package, including anti-assignment, SAM.gov UEI/CAGE, and SBA recertification checks. It clearly distinguishes this tool from siblings by naming `scan_far_dfars_clauses` and `generate_compliance_matrix` as alternatives for different workflows.

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 for GovCon M&A Contract Novation workflows and when to use alternatives: `scan_far_dfars_clauses` for general FAR/DFARS flow-down audits and `generate_compliance_matrix` for Section L/M requirement extraction. This gives an agent concrete routing criteria.

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