Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fac_get_findings

Read-only

Retrieve audit-risk findings for an entity from the Federal Audit Clearinghouse using either a UEI or report ID, with options for audit year and pagination.

Instructions

Drill into audit-RISK findings for an entity from the Federal Audit Clearinghouse (keyless via api.data.gov DEMO_KEY; api.fac.gov PostgREST findings table) — the risk-detail step after fac_search_audits. At least ONE of auditeeUei (12-char UEI) or reportId is REQUIRED (empty query refused); optional auditYear, limit (≤100, def 50), offset. Returns { findings:[{ report_id, auditee_uei, audit_year, award_reference, reference_number, is_material_weakness, is_modified_opinion, is_questioned_costs, is_repeat_finding, is_significant_deficiency, is_other_findings, is_other_matters, type_requirement, prior_finding_ref_numbers, riskFlags:{materialWeakness, modifiedOpinion, questionedCosts, repeatFinding, significantDeficiency, otherFindings, otherMatters} }] } + honest meta. ★RISK-FLAG HONESTY: is* flags surfaced VERBATIM ("Y"/"N") PLUS typed riskFlags tri-state ("Y"→true / "N"→false / blank/absent → null=UNKNOWN) — null NEVER rendered as false (the false-CLEAR class). ★EMPTY ≠ CLEAN: empty findings does NOT confirm a clean audit — the entity may not have filed a Single Audit (below the $750K threshold), may predate FAC coverage, or UEI wrong; a disclosure note fires on any empty result; on empty, confirm an ACCEPTED audit via fac_search_audits. ★PII: HARDCODED select-allowlist, entity + audit-risk fields only. totalAvailable is EXACT Content-Range total ('*'/absent → null + hedge, never 0); 400/403/5xx/timeout/HTML/non-array THROW. NOT a debarment/determination — cross-check SAM + OFAC. DEMO_KEY ~10 req/hr — set DATA_GOV_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page, 1..100, default 50.
offsetNo0-based row offset for pagination (default 0).
reportIdNoFilter by FAC report_id (^[0-9A-Za-z-]+$; → report_id=eq. — from a fac_search_audits row).
auditYearNoFilter by audit year (int, → audit_year=eq.).
auditeeUeiNoFilter by 12-char SAM UEI (^[A-Z0-9]{12}$; → auditee_uei=eq.).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds substantial behavioral disclosure: the verbatim 'Y'/'N' flags vs. tri-state riskFlags with null-as-unknown, the explicit 'empty ≠ clean' warning, exact Content-Range total semantics, error handling (throws on 400/403/5xx/timeout/HTML/non-array), PII allowlisting, and rate-limit caveats. This is far more than annotations alone and directly prevents misinterpretation.

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?

The description is long, but every sentence earns its place—it packs purpose, parameter constraints, return shape, honesty caveats, error behavior, and rate-limit notes into a dense but organized block. The most critical information (purpose and required parameters) is front-loaded, and the rest follows logically. It's verbose but not wasteful.

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?

Given there is no output schema, the description fully specifies the return object (findings array with field names and riskFlags object), the semantics of empty results, error conditions, and rate limits. For a complex tool with nuanced data interpretation, this is exceptionally complete. An agent has everything needed to call it correctly and interpret results 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?

The input schema covers all five parameters with descriptions at 100% coverage, so the schema already documents limit, offset, reportId, auditYear, and auditeeUei. The description adds a little extra context (e.g., 'from a fac_search_audits row' for reportId, and the requirement that at least one of auditeeUei or reportId must be set), but this is marginal beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific action ('Drill into audit-RISK findings') on a specific resource (Federal Audit Clearinghouse findings) and positions it as the risk-detail step after fac_search_audits, clearly distinguishing it from the sibling search tool. This is a precise, non-tautological purpose that an agent can act on immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly notes this is the step after fac_search_audits and requires at least one of auditeeUei or reportId. It also advises against using it for debarment/determination and says to cross-check SAM and OFAC. While it doesn't name a direct alternative beyond fac_search_audits, the context and exclusion (not a debarment tool) give solid guidance on when and when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools