Skip to main content
Glama

FacilityProof

by com.davisvillelabs
OverviewDiscussionsAdmin

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 $1.00 USD MPP operation when commerce is active in a released state. California, Texas, and Florida are currently released for paid full-compliance evidence. 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
NameRequiredDescriptionDefault
zipNoU.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.
cityNoCity for the physical facility. Used with name/address hints to distinguish facilities with similar names.
nameNoFacility or site name, including a distinguishing plant/site descriptor when available. For name-based resolution, also provide city/state, address, or ZIP whenever possible.
frsIdNoExact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly.
stateNoTwo-letter U.S. postal abbreviation for the physical facility. For full compliance evidence, California, Texas, and Florida are currently released. Permit identity uses a separate readiness gate.
addressNoStreet 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.
programIdNoExact 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 paid work.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfYesEvidence cutoff or as-of time represented by the report.
qualityYesQuality and coverage signals for the report.
evidenceYesSource-linked evidence observations supporting the report.
facilityYesResolved physical-facility identity, including authoritative identifiers and normalized location context.
programsYesBounded environmental program/permit coverage found for the resolved facility.
reportIdYesStable report identifier for this generated evidence package.
conflictsYesUnresolved disagreements across authoritative records that FacilityProof preserves rather than guessing through.
freshnessYesPer-source freshness and observation metadata so agents can judge staleness.
operationYesCanonical FacilityProof operation that produced this report.
penaltiesYesPenalty/monetary enforcement evidence linked to the resolved facility when supported.
sourceGapsYesExpected or relevant source coverage that could not be established or retrieved.
violationsYesReported violation/noncompliance evidence returned by authoritative sources; absence is not a clean-compliance conclusion.
generatedAtYesTimestamp when FacilityProof generated the report.
inspectionsYesInspection evidence returned by authoritative sources in the bounded search.
limitationsYesImportant scope and interpretation limits, including that the report is evidence rather than legal advice or a compliance verdict.
schemaVersionYesFacilityProof report schema version.
enforcementActionsYesFormal enforcement-action evidence returned by authoritative sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter U.S. postal abbreviation for the physical facility. For full compliance evidence, California and Texas are currently released; Florida is in development and unreleased. Permit identity uses a separate readiness gate."New value: +"Two-letter U.S. postal abbreviation for the physical facility. For full compliance evidence, California, Texas, and Florida are currently released. Permit identity uses a separate readiness gate."
  2. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter U.S. postal abbreviation for the physical facility. Full compliance evidence and permit identity have separate production-readiness rules."New value: +"Two-letter U.S. postal abbreviation for the physical facility. For full compliance evidence, California and Texas are currently released; Florida is in development and unreleased. Permit identity uses a separate readiness gate."
  3. Changed2 schema fields changed
    • changedInput schema / properties / programId / description
      Previous 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."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 paid work."
    • changedInput schema / properties / state / description
      Previous 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."New value: +"Two-letter U.S. postal abbreviation for the physical facility. Full compliance evidence and permit identity have separate production-readiness rules."
  4. Changed28 schema fields changed
    • 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."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With readOnlyHint=false but destructiveHint=false, the agent needs to know what side effect exists, and the description explains it: a $1.00 MPP charge, that identity/state eligibility are resolved before payment, that ambiguous/unresolved/unreleased requests are not charged, and that the call does not alter regulatory records. The idempotency nuance (fresh invocation can re-charge; settled-delivery retry must reuse the identical request and payment credential) goes well beyond the idempotentHint=false annotation and materially guides correct invocation.

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 core purpose and usage guidance are front-loaded, and the operational/billing sentences are dense rather than padded. It runs long, and the final sentence on settled-delivery retries is a lot of detail, but every sentence carries operative meaning for a paid, gated operation, so it stays efficient.

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?

An output schema exists, so return-value detail is not needed, and the description covers the remaining gaps an agent must know: identity-resolution strategy, released-state eligibility (CA/TX/FL), payment and non-charge conditions, and the read-but-charged side-effect profile. Nothing needed to call it correctly is missing.

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 description coverage is 100%, so the schema already documents each parameter, including the frsId-vs-name preference and the identity-hint role of zip/city. The description reinforces the resolution ordering (frsId/programId, else name plus location) and notes resolution happens pre-payment, but adds no new syntax or format meaning beyond the schema. 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 opens with a specific verb+resource ('Resolve one physical U.S. facility and return a bounded, source-reconciled environmental regulatory evidence report') and enumerates exactly what the report covers (air, water, hazardous-waste, drinking-water, inspections, violations, enforcement, penalties, freshness, gaps, conflicts). This scope is specific enough to distinguish it from the sibling permit-identity tool, which it also references.

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?

It states when to use it ('when an agent needs evidence about one specific facility and wrong-site matching or missing-source inference would be costly') and explicitly lists when not to ('company-wide research, raw EPA record retrieval, legal advice, or a clean/compliant verdict'). It also gives identity-resolution ordering (frsId/programId first, else name plus location), leaving nothing to inference.

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

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