Skip to main content
Glama
Sign In

signaltender-mcp

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

Audit DCAA Pre-Award Accounting System (SF 1408) & Indirect Rate Pools

audit_dcaa_accounting_sf1408
Read-onlyIdempotent

Audit a contractor's chart of accounts, indirect cost pool structure (Fringe, Overhead, G&A, B&P/IR&D), timekeeping procedures, labor distribution policy, and general ledger setup against the 18-point DCAA Standard Form 1408 (SF 1408) Pre-Award Accounting System Checklist, FAR 16.301-3, FAR Subpart 31.2, and DFARS 252.242-7006, returning an SF 1408 executive readiness overview, a line-by-line SF 1408 checklist audit, an indirect rate pool and allocation base analysis, a FAR 31.205 unallowable cost segregation assessment (with FAR 52.242-3 penalty risk), labor timekeeping and DCAA floor-check controls, and a pre-award survey remediation roadmap. This is a read-only, stateless, non-destructive GovCon accounting and compliance audit call (requires X-RapidAPI-Key; chart_of_accounts_and_pools_text accepts 20 to 45,000 characters, while target_contract_type_and_solicitation and accounting_software_and_erp_stack calibrate audit criteria across CPFF, CPIF, CPAF, T&M, and FFP contracts on Deltek Costpoint, Unanet, QuickBooks + GovCon timekeeping, or NetSuite). Use this tool when preparing for a DCAA SF 1408 Pre-Award Accounting System Survey, validating Fringe/Overhead/G&A pool-to-base causal/beneficial relationships, or segregating FAR 31.205 unallowable costs; use generate_igce_price_to_win instead to model proposal CLIN wrap-rate pricing and Price-to-Win sensitivity, or extract_pricing_schedule to parse Section B CLIN tables.

Input Schema

NameRequiredDescriptionDefault
chart_of_accounts_and_pools_textYesContractor's chart of accounts, indirect cost pool structure (Fringe, Overhead, G&A, B&P/IR&D), timekeeping procedures, labor distribution policy, and general ledger setup (20 to 45,000 characters).
accounting_software_and_erp_stackNoCurrent accounting ERP & timekeeping stack (e.g., Deltek Costpoint, Unanet GovCon, QuickBooks + ICAT/BigTime, NetSuite; defaults to 'QuickBooks_Online_With_GovCon_Timekeeping').QuickBooks_Online_With_GovCon_Timekeeping
target_contract_type_and_solicitationNoTarget contract type (CPFF, CPIF, CPAF, T&M, FFP) and solicitation SF 1408 / FAR 16.301-3 adequacy requirements (defaults to 'Cost_Plus_Fixed_Fee_CPFF_And_T_And_M').Cost_Plus_Fixed_Fee_CPFF_And_T_And_M

Output Schema

NameRequiredDescriptionDefault
statusNoExecution status ('success').
sf1408_18_point_checklistNoLine-by-line audit of Standard Form 1408 Section II accounting system adequacy criteria with findings and remediation steps.
sf1408_executive_overviewNoExecutive DCAA SF 1408 readiness verdict, compliance score (0-100), cost-reimbursable award eligibility, and summary.
indirect_rate_pool_and_base_analysisNoIndirect cost pool (Fringe, Overhead, G&A, B&P/IR&D) and allocation base audit under FAR 31.201-4 and CAS 418/410.
pre_award_survey_remediation_roadmapNoOrdered pre-audit action items and artifact checklist to pass the DCAA SF 1408 Pre-Award Accounting System Survey.
far_31_205_unallowable_cost_segregationNoAudit of FAR 31.205 expressly unallowable cost account segregation and FAR 52.242-3 penalty protection controls.
labor_timekeeping_and_floor_check_controlsNoEvaluation of daily labor timekeeping, supervisor approvals, Total Time Accounting (TTA), and DCAA floor-check readiness.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/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 safety profile is covered; the description redundantly restates 'read-only, stateless, non-destructive' but adds real value by disclosing the X-RapidAPI-Key auth requirement and the 20–45,000 character input bound. It stops short of describing rate limits, latency, or failure modes, keeping it below a 5.

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?

Two sentences, front-loaded with the audit action and its regulatory anchors, with the usage and exclusion clauses at the end. The parenthetical enumerations are dense and partly duplicate the schema descriptions (character bounds, ERP list), which costs a point but does not obscure the call decision.

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?

An output schema exists, so the enumerated deliverables are bonus context rather than a necessity; the description nonetheless covers inputs, auth, sizing, and alternatives. Near-complete, with the only shortfall being mild over-specification of return contents that the output schema already carries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the 3 baseline is already met, but the description goes further by explaining that the contract-type and ERP-stack parameters calibrate audit criteria across CPFF/CPIF/CPAF/T&M/FFP and across Costpoint/Unanet/QuickBooks/NetSuite — semantics the schema does not convey. It does not clarify what the defaults imply for the audit result, so it is not a 5.

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?

Names a specific verb (audit) and a precisely scoped resource: chart of accounts, indirect cost pools, timekeeping, labor distribution, and GL against the 18-point SF 1408 checklist plus FAR/DFARS references. It is unmistakable against siblings like generate_igce_price_to_win or extract_pricing_schedule, which it names 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?

Contains an explicit 'Use this tool when...' clause with three concrete triggers (SF 1408 survey prep, pool-to-base validation, FAR 31.205 segregation) and two explicit when-not redirects with the correct alternative for each. Routing is fully resolved by the description alone.

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