SignalTender B2B, GovCon & LegalTech MCP Server

Audit CAS Coverage (Modified vs. Full CAS) & Draft CASB Form DS-1 Disclosure Sections

generate_cost_accounting_cas_ds2

Read-onlyIdempotent

Determine Cost Accounting Standards (CAS / 48 CFR Chapter 99) exemptions vs. Modified CAS ($2M trigger contract / < $50M net CAS-covered awards) vs. Full CAS (>= $50M net CAS-covered awards or single award >= $50M) under FAR 52.230-1 through 52.230-6, audit contractor cost accounting practices against CAS 401, CAS 402, CAS 405, CAS 406, CAS 410 (Total Cost Input vs. Value-Added G&A base), and CAS 418, and generate paste-ready CASB Form DS-1 Disclosure Statement Continuation Sheet narratives across Parts I, II, III, IV, and VII plus FAR 52.230-6 General Dollar Magnitude (GDM) cost-impact governance rules. This is a read-only, stateless, non-destructive GovCon cost accounting compliance and disclosure generator (requires X-RapidAPI-Key; contractor_accounting_and_awards_profile accepts 20 to 45,000 characters, while target_cas_coverage_and_ds_form and g_and_a_allocation_base_preference calibrate Modified vs. Full CAS audits and CAS 410 G&A base distortion checks). Use this tool when determining FAR Part 30 CAS coverage tiers, auditing CAS 401-420 compliance, or drafting a CASB Form DS-1 Disclosure Statement; use audit_dcaa_accounting_sf1408 instead for pre-award Standard Form 1408 accounting system surveys, or generate_igce_price_to_win for proposal LCAT wrap-rate pricing.

Input Schema

Name	Required	Description	Default
`target_cas_coverage_and_ds_form`	No	Target CAS coverage evaluation and disclosure form (CAS Exemption Audit, Modified CAS 401/402/405/406, Full CAS 19 Standards, or CASB DS-1 / DS-2 Disclosure Statement preparation; defaults to 'Full_CAS_19_Standards_Transition_And_CASB_DS1_Disclosure_Statement').	Full_CAS_19_Standards_Transition_And_CASB_DS1_Disclosure_Statement
`g_and_a_allocation_base_preference`	No	CAS 410 G&A allocation base preference (Total Cost Input [TCI], Value-Added Cost Input excluding direct material/subcontracts, or Single Element Cost Input; defaults to 'Evaluate_Total_Cost_Input_TCI_vs_Value_Added_Base_Under_CAS_410').	Evaluate_Total_Cost_Input_TCI_vs_Value_Added_Base_Under_CAS_410
`contractor_accounting_and_awards_profile`	Yes	Contractor business size status, prior/current year net CAS-covered awards, contract types, direct vs. indirect charging rules, Fringe/Overhead/G&A pool structures, and pass-through subcontract volume (20 to 45,000 characters).

Output Schema

Name	Required	Description
`status`	No	Execution status ('success').
`core_cas_standards_compliance_audit`	No	Audit of CAS 401, CAS 402, CAS 405, CAS 406, CAS 410, and CAS 418 compliance against DCAA CAM Chapter 8.
`casb_ds1_disclosure_statement_sections`	No	Paste-ready CASB Form DS-1 Disclosure Statement Continuation Sheet narratives across Parts I, II, III, IV, and VII.
`cas_applicability_and_coverage_determination`	No	48 CFR 9903 CAS exemption vs. Modified CAS vs. Full CAS determination and FAR 52.230 clause mapping.
`far_52_230_6_cost_impact_and_change_governance`	No	FAR 52.230-6 60-day CFAO advance notice rules and General Dollar Magnitude (GDM) cost-impact governance.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's "read-only, stateless, non-destructive" restates structured data. The one genuine addition is the auth requirement ("requires X-RapidAPI-Key"), and it reiterates the schema's character bounds rather than disclosing anything new about invocation behavior or output shaping.

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?

Purpose is front-loaded, but the core content is delivered as one sprawling run-on sentence with stacked parentheticals (dollar thresholds, CAS numbers, TCI-vs-Value-Added asides) that are hard to parse. The single-sentence usage/routing clause at the end is efficient; the middle is dense and could be broken into scannable clauses without losing content.

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?

An output schema exists so return values need not be explained. Between the CAS tier thresholds, the covered standards, the DS-1 parts, the GDM governance angle, the auth requirement, and routing to two alternatives, an agent has everything needed to decide and call correctly.

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?

With 100% schema description coverage, the schema already documents all three parameters, including the 20–45,000 character range restated verbatim in the description. The description does add framing that the two optional params calibrate Modified vs. Full CAS audits and CAS 410 G&A base distortion, which is modest added value beyond the schema text — the baseline 3 applies.

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 names a precise verb+resource set: determining CAS exemption vs. Modified CAS vs. Full CAS coverage, auditing practices against CAS 401/402/405/406/410/418, and generating CASB Form DS-1 narratives and GDM rules. It is unmistakably distinct from siblings like `audit_dcaa_accounting_sf1408` (SF 1408 surveys) and `generate_igce_price_to_win` (LCAT wrap rates), which are named explicitly.

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 triggering conditions are given ("Use this tool when determining FAR Part 30 CAS coverage tiers, auditing CAS 401-420 compliance, or drafting a CASB Form DS-1") plus two named alternatives with the conditions that select them. Nothing about tool selection is left 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 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.