Skip to main content
Glama
Sign In

signaltender-mcp

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

Audit DCSA Facility Clearance (FCL), DD Form 254 & FOCI Mitigation

audit_foci_dd254_clearance
Read-onlyIdempotent

Audit DD Form 254 Contract Security Classification Specifications (Blocks 10, 11, 13), Standard Form 328 (SF 328 — Certificate Pertaining to Foreign Interests), and corporate cap-table / foreign investor structures against 32 CFR Part 117 (NISPOM) and Defense Counterintelligence and Security Agency (DCSA) Facility Clearance (FCL) and Foreign Ownership, Control, or Influence (FOCI) mitigation standards, returning an FCL & FOCI executive overview, a DD Form 254 Block 10/11 safeguarding matrix (COMSEC, SCI, SIPRNet, CUI), an SF 328 foreign interest factor audit, a DCSA FOCI mitigation agreement blueprint (Board Resolution, SCA, SSA with NID, or Proxy/Voting Trust with ECP and TCP controls), and a Key Management Personnel (KMP) Exclusion Resolution & NISP eMASS checklist. This is a read-only, stateless, non-destructive industrial security audit call (requires X-RapidAPI-Key; dd254_and_ownership_cap_table_text accepts 20 to 45,000 characters, while target_facility_clearance_level and foreign_ownership_and_board_context calibrate DCSA FCL safeguarding and 32 CFR 117.11 FOCI mitigation instruments). Use this tool when auditing DD Form 254 classified safeguarding requirements, SF 328 foreign ownership/LP triggers, or DCSA FCL / FOCI mitigation agreements; use generate_ato_rmf_package instead for DoD RMF / Continuous ATO (cATO) NIST 800-53 System Security Plans, or match_key_personnel for individual candidate security clearance and LCAT resume verification.

Input Schema

NameRequiredDescriptionDefault
target_facility_clearance_levelNoRequired Facility Clearance (FCL) and safeguarding posture (e.g., Confidential, Secret, Top Secret, TS/SCI, COMSEC, SIPRNet, JWICS; defaults to 'Top_Secret_FCL_With_SCI_And_SIPRNet').Top_Secret_FCL_With_SCI_And_SIPRNet
dd254_and_ownership_cap_table_textYesDD Form 254 Contract Security Classification Specification text (Blocks 10, 11, 13), SF 328 Certificate Pertaining to Foreign Interests entries, and corporate cap-table / foreign investor ownership structure (20 to 45,000 characters).
foreign_ownership_and_board_contextNoSummary of foreign equity voting/ownership percentages, foreign board seats, foreign debt, or foreign technology licensing ties under 32 CFR Part 117 (NISPOM; defaults to 'Minority_Foreign_LP_Or_Board_Seat_Under_Review').Minority_Foreign_LP_Or_Board_Seat_Under_Review

Output Schema

NameRequiredDescriptionDefault
statusNoExecution status ('success').
fcl_and_foci_executive_overviewNoHigh-level DCSA Facility Clearance (FCL) eligibility verdict, FOCI severity tier, and recommended mitigation instrument.
sf328_foreign_interest_factor_auditNoEvaluation of Standard Form 328 (Certificate Pertaining to Foreign Interests) triggers across foreign equity, LP feeders, board seats, debt, and revenue.
dcsa_foci_mitigation_agreement_blueprintNoStructured DCSA FOCI mitigation blueprint (Board Resolution, SCA, SSA, or Proxy/Voting Trust) with Outside Director, ECP, and TCP controls.
dd254_block10_and_11_safeguarding_matrixNoBlock-by-block audit of DD Form 254 Block 10, 11, and 13 classified access, safeguarding, COMSEC, SCI, and SIPRNet mandates under 32 CFR Part 117.
kmp_exclusion_resolution_and_nisp_emass_checklistNoStep-by-step Key Management Personnel (KMP) List, Board Exclusion Resolution, DISS, and NISP eMASS submission checklist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / dd254_block10_and_11_safeguarding_matrix / description
      Previous value: -"Block-by-block audit of DD Form 254 Block 10, 11, and 13 classified access, safeguarding, COMSEC, SCI, and SIPRNet mandates."New value: +"Block-by-block audit of DD Form 254 Block 10, 11, and 13 classified access, safeguarding, COMSEC, SCI, and SIPRNet mandates under 32 CFR Part 117."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld=false, and the description adds non-redundant behavior: it is stateless, requires an X-RapidAPI-Key header, and enumerates the five artifacts produced (FCL/FOCI overview, safeguarding matrix, SF 328 factor audit, mitigation agreement blueprint, KMP exclusion/eMASS checklist). That tells the agent what it will actually get back and what credentials are needed before calling.

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 and scope are front-loaded, but the first sentence is a sprawling run-on that enumerates five deliverables whose structure is already defined by the output schema. The repetition of read-only/stateless/non-destructive and the character limits already in the schema adds bulk without new signal.

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 high-complexity, multi-standard audit tool, the description supplies the regime (NISPOM/32 CFR 117), the input expectations, credential requirements, output artifacts, and sibling routing. With an output schema present and rich annotations, nothing essential for a correct invocation is missing.

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 baseline is 3, but the description adds causal meaning beyond the schema: it explains that target_facility_clearance_level and foreign_ownership_and_board_context act as calibration knobs for DCSA safeguarding and 32 CFR 117.11 mitigation instruments, not just labels. The 20–45,000 character bound on the text param merely restates schema constraints.

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?

Specific verb (audit) plus named resources (DD Form 254 Blocks 10/11/13, SF 328, cap-table/foreign investor structures) against named standards (32 CFR Part 117 NISPOM, DCSA FCL/FOCI). It explicitly separates itself from generate_ato_rmf_package (RMF/cATO) and match_key_personnel (individual clearances), so an agent can route correctly without opening any schema.

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...' trigger list (DD 254 classified safeguarding, SF 328 foreign ownership/LP triggers, FCL/FOCI mitigation agreements) and names two concrete alternatives with the conditions that select them. Both inclusion and exclusion guidance are present.

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