FacilityProof

Check facility compliance evidence

facilityproof.check_facility_compliance_evidence

Resolve one physical U.S. facility and return a bounded, source-reconciled environmental regulatory evidence report covering core air, water, hazardous-waste, and drinking-water programs plus inspections, reported violations, formal enforcement, penalties, freshness, source gaps, and conflicts. Use when an agent needs evidence about one specific facility and wrong-site matching or missing-source inference would be costly; do not use for company-wide research, raw EPA record retrieval, legal advice, or a clean/compliant verdict. Provide frsId or programId when known; otherwise provide name with enough location context to resolve exactly one site. This is a $15.00 MPP operation when commerce is active in a released state: identity and state eligibility are resolved before payment, ambiguous/unresolved/unreleased requests are not charged, and the call does not alter regulatory records. A fresh authorized invocation can charge again, while a settled delivery retry should reuse the identical request with the same payment credential to recover without a second settlement.

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	U.S. ZIP or ZIP+4 for the physical facility. Use as an identity hint, not as a substitute for a site name or authoritative identifier.
`city`	No	City for the physical facility. Used with name/address hints to distinguish facilities with similar names.
`name`	No	Facility or site name, including a distinguishing plant/site descriptor when available. For name-based resolution, also provide city/state, address, or ZIP whenever possible.
`frsId`	No	Exact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly.
`state`	No	Two-letter U.S. postal abbreviation for the physical facility, such as CA. Current paid production release is California only; unreleased states are rejected before payment.
`address`	No	Street address for the physical facility when known. Used only for physical-site identity resolution; do not provide corporate headquarters unless that is the facility being checked.
`programId`	No	Exact authoritative environmental program identifier when known, such as an NPDES permit ID or RCRA handler ID. FacilityProof uses it to resolve the physical facility before evidence retrieval.

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	Yes	Evidence cutoff or as-of time represented by the report.
`quality`	Yes	Quality and coverage signals for the report.
`evidence`	Yes	Source-linked evidence observations supporting the report.
`facility`	Yes	Resolved physical-facility identity, including authoritative identifiers and normalized location context.
`programs`	Yes	Bounded environmental program/permit coverage found for the resolved facility.
`reportId`	Yes	Stable report identifier for this generated evidence package.
`conflicts`	Yes	Unresolved disagreements across authoritative records that FacilityProof preserves rather than guessing through.
`freshness`	Yes	Per-source freshness and observation metadata so agents can judge staleness.
`operation`	Yes	Canonical FacilityProof operation that produced this report.
`penalties`	Yes	Penalty/monetary enforcement evidence linked to the resolved facility when supported.
`sourceGaps`	Yes	Expected or relevant source coverage that could not be established or retrieved.
`violations`	Yes	Reported violation/noncompliance evidence returned by authoritative sources; absence is not a clean-compliance conclusion.
`generatedAt`	Yes	Timestamp when FacilityProof generated the report.
`inspections`	Yes	Inspection evidence returned by authoritative sources in the bounded search.
`limitations`	Yes	Important scope and interpretation limits, including that the report is evidence rather than legal advice or a compliance verdict.
`schemaVersion`	Yes	FacilityProof report schema version.
`enforcementActions`	Yes	Formal enforcement-action evidence returned by authoritative sources.

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedSep 21, 2026

addedInput schema / description

Added value: +"Identity hints for one physical U.S. facility. Provide an exact EPA FRS ID or authoritative program ID when known; otherwise provide the facility name plus enough location context to resolve one site safely. FacilityProof fails closed on ambiguous identity."

addedInput schema / properties / address / description

Added value: +"Street address for the physical facility when known. Used only for physical-site identity resolution; do not provide corporate headquarters unless that is the facility being checked."

addedInput schema / properties / city / description

Added value: +"City for the physical facility. Used with name/address hints to distinguish facilities with similar names."

changedInput schema / properties / frsId / description

Previous value: -"EPA Facility Registry Service identifier when known."New value: +"Exact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly."

changedInput schema / properties / name / description

Previous value: -"Facility or site name."New value: +"Facility or site name, including a distinguishing plant/site descriptor when available. For name-based resolution, also provide city/state, address, or ZIP whenever possible."

changedInput schema / properties / programId / description

Previous value: -"Authoritative program identifier such as an NPDES or RCRA ID when known."New value: +"Exact authoritative environmental program identifier when known, such as an NPDES permit ID or RCRA handler ID. FacilityProof uses it to resolve the physical facility before evidence retrieval."

addedInput schema / properties / state / description

Added value: +"Two-letter U.S. postal abbreviation for the physical facility, such as CA. Current paid production release is California only; unreleased states are rejected before payment."

addedInput schema / properties / zip / description

Added value: +"U.S. ZIP or ZIP+4 for the physical facility. Use as an identity hint, not as a substitute for a site name or authoritative identifier."

addedOutput schema / description

Added value: +"Bounded, source-reconciled environmental regulatory evidence report for one resolved physical facility. Missing records remain source gaps and conflicts remain explicit rather than becoming a compliance verdict."

addedOutput schema / properties / asOf / description

Added value: +"Evidence cutoff or as-of time represented by the report."

addedOutput schema / properties / conflicts / description

Added value: +"Unresolved disagreements across authoritative records that FacilityProof preserves rather than guessing through."

addedOutput schema / properties / enforcementActions / description

Added value: +"Formal enforcement-action evidence returned by authoritative sources."

addedOutput schema / properties / evidence / description

Added value: +"Source-linked evidence observations supporting the report."

addedOutput schema / properties / facility / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / facility / description

Added value: +"Resolved physical-facility identity, including authoritative identifiers and normalized location context."

addedOutput schema / properties / freshness / description

Added value: +"Per-source freshness and observation metadata so agents can judge staleness."

addedOutput schema / properties / generatedAt / description

Added value: +"Timestamp when FacilityProof generated the report."

addedOutput schema / properties / inspections / description

Added value: +"Inspection evidence returned by authoritative sources in the bounded search."

addedOutput schema / properties / limitations / description

Added value: +"Important scope and interpretation limits, including that the report is evidence rather than legal advice or a compliance verdict."

addedOutput schema / properties / operation / description

Added value: +"Canonical FacilityProof operation that produced this report."

addedOutput schema / properties / penalties / description

Added value: +"Penalty/monetary enforcement evidence linked to the resolved facility when supported."

addedOutput schema / properties / programs / description

Added value: +"Bounded environmental program/permit coverage found for the resolved facility."

addedOutput schema / properties / quality / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / quality / description

Added value: +"Quality and coverage signals for the report."

addedOutput schema / properties / reportId / description

Added value: +"Stable report identifier for this generated evidence package."

addedOutput schema / properties / schemaVersion / description
```
Added value: +"FacilityProof report schema version."
```

addedOutput schema / properties / sourceGaps / description

Added value: +"Expected or relevant source coverage that could not be established or retrieved."

addedOutput schema / properties / violations / description

Added value: +"Reported violation/noncompliance evidence returned by authoritative sources; absence is not a clean-compliance conclusion."

First observedSep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations are sparse (four boolean hints), and the description shoulders the behavioral burden admirably. It discloses the $15.00 MPP charge, the pay-after-resolution ordering (identity and state eligibility resolved before payment), that ambiguous/unresolved/unreleased requests are free, that the call does not alter regulatory records, and the exact retry semantics for avoiding double settlement. This substantially deepens the idempotentHint=false and readOnlyHint=false annotations by explaining the nature of side effects.

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: purpose, usage, parameter strategy, and cost semantics are cleanly sequenced with the most decision-relevant information (scope) front-loaded. The payment/retry sentence is dense and complex, which keeps it from a 5, but it carries essential invocation information that cannot be safely omitted.

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 moderately complex tool with 7 parameters, an anyOf-required constraint, and an output schema, the description covers everything an agent needs: what is returned, when to invoke, which identifiers to supply, resolution failure behavior, state restrictions, and cost. The output schema handles return-value documentation, so no description redundancy is needed.

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?

Schema coverage is 100%, so the baseline is 3 — the schema already documents every parameter including hints like 'Prefer this over name matching' for frsId. The description adds modest value by stating the resolution hierarchy ('Provide frsId or programId when known; otherwise provide name with enough location context'), but this mostly restates what the parameter descriptions already convey.

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 opens with a specific verb+resource combination — 'Resolve one physical U.S. facility and return a bounded, source-reconciled environmental regulatory evidence report' — and enumerates the exact report contents (air, water, hazardous-waste, drinking-water programs, inspections, violations, enforcement, penalties, freshness, source gaps). It leaves no ambiguity about what the tool produces or its unit of work.

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?

Provides explicit when-to-use ('when an agent needs evidence about one specific facility and wrong-site matching or missing-source inference would be costly') and a concrete do-not-use list (company-wide research, raw EPA record retrieval, legal advice, clean/compliant verdict). With no siblings present, this exclusion list fully substitutes for alternative routing.

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

All FacilityProof 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.

Resources

Need Help?