Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesApify API token used to run CivicDataForge Actors.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
str-permit-registryA

Use for address, owner, permit-ID, or jurisdiction research across supported US short-term-rental permit sources. For Florida statewide DBPR lodging licenses, use fl-dbpr-vacation-rentals instead. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

fl-dbpr-vacation-rentalsA

Use for Florida statewide DBPR vacation-rental and lodging-license evidence. For municipal STR permits use str-permit-registry; for code violations use property-violations. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

property-violationsA

Use for municipal building, property, and code-violation research in supported jurisdictions. Do not use for STR licensing or restaurant health inspections; choose the corresponding permit or inspection tool. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

leie-exclusion-screeningA

Use to find review candidates in the HHS-OIG LEIE by name, valid NPI, state, specialty, or exclusion type. Do not treat a candidate match as identity adjudication or use this tool for facility licensing. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without changing the source list.

restaurant-inspection-scoresA

Use for official restaurant inspection scores, violations, and facility-history research in supported jurisdictions. Do not use for general property-code violations or childcare inspections. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

multistate-childcare-licensingA

Use for cross-state childcare licensing, inspection, and deficiency research across supported states. For Texas-only operation, inspection, or deficiency filters, use texas-childcare-licensing instead. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

texas-childcare-licensingA

Use for Texas-only childcare operation, inspection, and deficiency evidence. For comparable research spanning multiple supported states, use multistate-childcare-licensing instead. Starts the bound Apify Actor with the caller's APIFY_TOKEN, may consume Apify usage, waits up to 60 seconds, and returns at most 1,000 source-linked rows without modifying government records.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct data domain (STR permits, Florida DBPR, property violations, LEIE exclusion, restaurant inspections, childcare licensing), and the descriptions explicitly cross-reference other tools to steer agents away from misselection. The two childcare tools are clearly separated by geographic scope, eliminating ambiguity.

Naming Consistency4/5

All tool names follow a consistent lowercase-hyphenated style, which is predictable and readable. However, they are noun phrases rather than a verb_noun pattern (e.g., 'property-violations' vs. 'search_permits'), so while the convention is consistent, it deviates from the common verb-first structure.

Tool Count5/5

With 7 tools, the server is well-scoped for its stated purpose of civic data research. Each tool covers a specific, non-trivial dataset, and the count is neither too thin nor overwhelming for agents to navigate.

Completeness4/5

The tool set covers major civic data categories (permits, violations, health inspections, exclusion screening, childcare licensing) with no obvious dead ends. Minor gaps exist, such as general business licensing or building permits across all states, but the current surface is coherent for the intended domain.

Maintenance

ActivityActive
ResponsivenessNo issues