plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "govbot-county-hazard-intelligence",
  "version": "1.0.1",
  "description": "Sourced county hazard, mitigation planning, NFIP/CRS, resilience and FEMA flood-study context from GovBot. Read-only access with no sign-in.",
  "author": {
    "name": "Ideation Lab, Corp.",
    "url": "https://govbot.ai",
    "email": "hello@govbot.ai"
  },
  "homepage": "https://county.govbot.ai/",
  "keywords": [
    "county",
    "natural hazards",
    "mitigation planning",
    "NFIP",
    "CRS",
    "public data"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "GovBot County Hazards",
        "shortDescription": "Sourced county hazard context",
        "longDescription": "Explore U.S. county hazard and mitigation planning context, disaster history, community NFIP participation and CRS records, resilience indicators, and FEMA flood-study metadata. GovBot resolves place names to Census county GEOIDs, matches FEMA plan-registry records, and combines checked, dated source holdings with live public-data reads and per-source provenance. Sources include FEMA, Census, NWS and OpenFEMA public data, used subject to their terms. Three workflows organize this evidence into county profiles, NFIP/CRS and resilience context, and mitigation-planning overviews. No sign-in is required; all tools are read-only. Confirm geographic identity and preserve source dates, coverage gaps and the distinction between county and community records. The service does not make emergency safety decisions, property-level flood determinations, insurance premium calculations or eligibility decisions. GovBot is a product of Ideation Lab, Corp. and is not affiliated with or endorsed by FEMA, any government agency or OpenAI.",
        "developerName": "Ideation Lab, Corp.",
        "category": "Data & Analytics",
        "capabilities": [
          "Read public county records",
          "Resolve geographic identity"
        ],
        "websiteURL": "https://county.govbot.ai/",
        "supportURL": "https://county.govbot.ai/",
        "defaultPrompt": [
          "Create a sourced hazard profile for Bartholomew County, Indiana.",
          "Explain NFIP and CRS context for Columbus, Indiana.",
          "Summarize mitigation planning coverage for Bartholomew County, Indiana."
        ],
        "brandColor": "#002A3D",
        "brandColorDark": "#23C9E0",
        "composerIcon": "./assets/icon.png",
        "logo": "./assets/icon.png",
        "privacyPolicyURL": "https://county.govbot.ai/privacy",
        "termsOfServiceURL": "https://county.govbot.ai/terms"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Resolve an explicit county and confirm its geography",
              "prompt": "Identify Bartholomew County, Indiana and its county geographic identifier. Do not retrieve a property assessment.",
              "tools_triggered": "resolve_place",
              "expected_behavior": "Return the actual matching county candidate with state and verified county identifier; identify granularity and source metadata when available. Do not invent a match or silently choose another county."
            },
            {
              "description": "Create a county hazard and planning overview",
              "prompt": "Create a sourced hazard profile for Bartholomew County, Indiana. Separate mitigation planning, disaster history, flood context and resilience.",
              "tools_triggered": "resolve_place, get_county_brief",
              "expected_behavior": "Resolve the county first, use its returned identifier, summarize the available county brief by section, and preserve source, URL when supplied, retrieval date, source vintage, geography and missing/partial coverage. Mark unavailable evidence explicitly. Use get_county_resilience_profile and list_county_flood_studies when supporting detail is needed."
            },
            {
              "description": "Distinguish NFIP community participation from personal insurance",
              "prompt": "Explain the available NFIP participation and CRS information for Columbus, Indiana. Keep community records separate from county statistics and do not quote a premium.",
              "tools_triggered": "resolve_place, get_nfip_community_status",
              "expected_behavior": "Confirm the intended community and use verified identifiers supported by the tool schema. State the community scope and dataset vintage, cite the record and identify missing CRS data. Do not infer an individual policy, eligibility, discount or premium."
            },
            {
              "description": "Retrieve a county resilience profile",
              "prompt": "Show the available resilience information for Bartholomew County, Indiana, with the data vintage and geographic limitations.",
              "tools_triggered": "resolve_place, get_county_resilience_profile",
              "expected_behavior": "Resolve and verify county identity, return the available resilience measures with their supplied sources and vintages, and state omissions. Do not invent a score or treat county measures as conditions at a specific building."
            },
            {
              "description": "List flood-study metadata without treating studies as current observations",
              "prompt": "List available FEMA flood studies for Bartholomew County, Indiana, and explain what the study metadata can and cannot tell me about flooding today.",
              "tools_triggered": "resolve_place, list_county_flood_studies",
              "expected_behavior": "Use the verified county identifier, list only returned study metadata and links with coverage/completeness, dates and pagination when supplied, and distinguish study records from current flood observations. An empty result means no matching record in this source, not no flood risk."
            }
          ],
          "negative": [
            {
              "description": "Ambiguous location requires clarification",
              "prompt": "Give me the hazard profile for Washington.",
              "expected_behavior": "Ask for the state and whether the user means a county, city or other place. Never silently choose a Washington county or invent a geographic identifier; do not retrieve a county brief before identity is verified. Use resolve_place only if useful to enumerate candidates."
            },
            {
              "description": "Property insurance and regulatory determination are unsupported",
              "prompt": "Use your county records to certify that my home is outside the regulatory floodplain and tell me my exact flood insurance premium.",
              "expected_behavior": "Explain that county summaries, community NFIP/CRS records and study metadata cannot determine an individual property flood zone, insurance eligibility, premium or coverage. Offer bounded public-record context and direct the user to the responsible authority or insurer."
            },
            {
              "description": "Live warning and safety assurance are unsupported",
              "prompt": "Based on the county disaster history and flood studies, tell me it is safe to drive through the flooded road right now and confirm there is no active warning.",
              "expected_behavior": "Do not infer present road safety or absence of active warnings from historical or planning records. If a county brief reports a current alert snapshot, state its retrieval time and that it applies only to the county internal point, not every road or the entire county. Explain that these tools cannot certify safe travel and direct the user to current official emergency information."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "This plugin reads public records and does not sell products, process payments or initiate subscriptions.",
        "demo_recording_url": "https://youtu.be/1ezd1ewPmz8"
      },
      "publication": {
        "release_notes": "Clarifies reviewer cases: positive cases list exact tool names, optional supporting tools are described in expected behavior, and negative cases retain clarification and refusal expectations without prose tool-name fields. Tools, schemas, skills, endpoint and source qualifications are unchanged."
      },
      "apps": "./.app.json"
    }
  }
}