Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fac_get_findings

Read-only

Retrieve audit-risk findings for an entity from FAC using UEI or report ID. Returns material weakness, modified opinion, questioned costs, and other flags.

Instructions

Drill into the audit-RISK findings for an entity from the Federal Audit Clearinghouse (keyless via the 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 → auditee_uei) or reportId (→ report_id, from a fac_search_audits row) is REQUIRED (an empty query is refused, never a whole-table scan); optional auditYear (int), 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: the is* flags are surfaced VERBATIM as the auditor reported them ("Y"/"N") PLUS a typed riskFlags tri-state ("Y"→true / "N"→false / blank/absent/other → null=UNKNOWN) — a null flag is NEVER rendered as false/"no material weakness" (the false-CLEAR class). ★EMPTY ≠ CLEAN: an empty findings list does NOT confirm a clean audit — the entity may not have filed a Single Audit (below the $750K threshold), the audit may predate FAC coverage, or the UEI may be wrong; a disclosure note fires on any empty result telling you to confirm an ACCEPTED audit exists via fac_search_audits. ★PII: a HARDCODED select-allowlist (NO caller column param) surfaces only entity + audit-risk fields — no personal contact. totalAvailable is the EXACT Content-Range total ('*'/absent ⇒ null + hedge, never 0); a bad column ⇒ 400 ⇒ invalid_input; 400/403/5xx/timeout/HTML/non-array THROW (206 = success). NOT a debarment/determination — cross-check SAM exclusions + OFAC + the specific finding text. Keyless-first via DEMO_KEY (~10 req/hr; set DATA_GOV_API_KEY — never logged).

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.).
Behavior5/5

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

The description adds significant context beyond annotations: risk-flag honesty (tri-state vs false-CLEAR), empty results not implying clean audit, PII protection via hardcoded select-allowlist, totalAvailable behavior, error handling (400/403/5xx throw), and rate limiting for DEMO_KEY. No contradictions with annotations (readOnlyHint and openWorldHint are consistent).

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 well-structured with bullet points and emojis, packing a lot of information efficiently. It is somewhat lengthy, but every sentence adds essential detail. A slight reduction in verbosity could improve conciseness, but it remains effective.

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?

Given the complexity of the tool (nuanced risk flags, empty results, PII, error handling) and the lack of an output schema, the description covers most critical aspects: purpose, parameters, behavior, limitations, and caveats. It partially describes the return structure (findings array with riskFlags). While more detail on output shape could help, it is sufficiently complete for proper usage.

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%, but the description adds value by indicating that at least one of auditeeUei or reportId is required (schema says all optional), mapping field names (auditeeUei → auditee_uei, reportId → report_id), and specifying limit's maximum and default. This goes beyond the schema, justifying a score above baseline 3.

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 clearly states the verb 'Drill into' and identifies the resource as 'audit-RISK findings for an entity from the Federal Audit Clearinghouse.' It also distinguishes itself from sibling tools by noting it is 'the risk-detail step after fac_search_audits,' making its purpose unambiguous.

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?

The description explicitly states the required parameters ('At least ONE of auditeeUei or reportId'), provides defaults and limits, and warns against using it for debarment determination. It also explains how to interpret empty results and suggests cross-referencing with fac_search_audits, giving clear guidance on when and how to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cliwant/mcp-sam-gov'

If you have feedback or need assistance with the MCP directory API, please join our Discord server