Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_daily_manager_briefingA

Generate the daily executive briefing and prioritized action plan for permit managers.

Synthesizes portfolio health, overnight status transitions, expiring contractor insurance, and provides an itemized task matrix with assigned roles, deadlines, and unblocking actions.

Use this tool during morning standups or management planning sessions when asked: "Give me today's permit briefing", "What should the team work on today?", or "What are our top permitting priorities?"

Returns: A formatted executive briefing with portfolio health score, key changes, systemic bottlenecks, and an itemized action task list.

intake_project_scopeA

Autonomous Project Scope Ingestion Agent.

Parses unformatted contractor Scopes of Work (SOWs), determines municipal AHJ jurisdiction from the address, identifies required trade sub-permits, verifies commercial Arizona PE structural stamping thresholds, and scaffolds a draft permit.

Args: scope_description: Plain language contractor SOW (e.g. "Replace rooftop HVAC units and upgrade 400A panel"). address: Physical jobsite address (e.g. "4800 E Camelback Rd, Phoenix, AZ"). valuation: Estimated total construction valuation in USD. project_name: Optional development project name.

Returns: Structured intake summary with detected city, required trade permits, legal engineering stamp triggers, and mandatory submittal checklist.

estimate_permit_fees_and_slaB

Municipal Permit Fee & Plan Review SLA Turnaround Calculator.

Estimates municipal application fees, plan check surcharges, technology fees, and review turnaround timelines across Phoenix, Scottsdale, Tempe, and Mesa.

Args: jurisdiction: Target city jurisdiction (e.g. "City of Phoenix", "City of Tempe"). permit_type: Trade type (e.g. "mechanical", "electrical", "building"). valuation: Declared construction valuation in USD.

Returns: Itemized municipal fee breakdown and estimated review turnaround SLA.

search_permit_requirementsA

Section-Aware Municipal Building Code RAG Search (Rule 3).

Queries the local section-aware RAG engine of municipal building codes, local amendments, and technical guidelines (e.g. Phoenix Mechanical Code 301.5, ASHRAE 90.1, NEC 2023). Achieves ~82.9% context token reduction compared to raw manual dumping.

Args: query: Building code search query (e.g., "rooftop unit structural calculations Phoenix"). jurisdiction: Optional filter (e.g., "City of Phoenix"). permit_type: Optional trade filter (e.g., "mechanical", "electrical"). top_k: Number of relevant code sections to retrieve (default: 4).

Returns: Precise building code citations, section numbers, relevance scores, and excerpts.

check_permit_readinessA

Pre-Submission Readiness Audit & Blocker Breakdown Gate.

Performs an exhaustive pre-filing audit of a single permit: calculates a composite 0–100 readiness score, categorizes risk (LOW, MEDIUM, HIGH, BLOCKED), identifies unverified/expired documents, open authority comments, and issues a Go/No-Go verdict.

Args: permit_id: Permit identifier (e.g., "P-1042").

Returns: Comprehensive readiness report with score, risk tier, blocker breakdown, and actions.

generate_formal_ahj_response_packetA

Official Municipal Plan-Check Response Letter Generator (Rule 2).

Compiles a formal Comment-by-Comment Transmittal Letter resolving examiner objections with code citations, revision cloud references, and an explicit Human-in-the-Loop Professional Engineer (PE) verification gate before municipal upload.

Args: permit_id: Permit identifier (e.g. "P-1042").

Returns: Official city response transmittal letter ready for engineer stamp and filing.

verify_contractor_registrationA

Contractor ROC License & General Liability Insurance Compliance Audit.

Audits Arizona Registrar of Contractors (ROC) standing, verifies trade classifications, and audits mandatory $1,000,000 General Liability Insurance policies, expiration dates, and municipal Additional Insured endorsements.

Args: contractor_name: Name of the general or specialty contractor (e.g. "Ironclad Construction"). jurisdiction: Target city jurisdiction (e.g. "City of Phoenix", "City of Tempe"). permit_type: Permitted trade type (e.g. "mechanical", "electrical", "building").

Returns: Structured compliance verification report with license and insurance status.

Prompts

Interactive templates invoked by user choice

NameDescription
daily_standup_briefingPrompt to prepare and conduct the daily morning permitting standup meeting. Directs the LLM to inspect portfolio priorities, overnight changes, and systemic blockers, then formulate a crisp standup agenda with assigned owners and actions.
permit_readiness_auditPrompt for conducting an exhaustive, audit-grade readiness check on a single permit. Directs the LLM to verify documents, check applicable requirements, inspect open reviewer comments, evaluate inspection milestones, and synthesize a go/no-go recommendation.
resubmission_strategyPrompt for crafting a tactical resubmission plan for a rejected or revision-required permit. Directs the LLM to create a plan addressing all examiner objections, preparing a written response matrix, and establishing a submission timeline.
portfolio_risk_reviewPrompt for leadership-level quarterly/monthly permit portfolio risk review. Directs the LLM to evaluate all permits, surface systemic bottlenecks, detect schedule slippages, and recommend strategic operational improvements.

Resources

Contextual data attached and managed by the client

NameDescription
get_portfolio_summary_resourceGet high-level portfolio health KPIs, risk breakdown, and active permit counts.
get_portfolio_priorities_resourceGet full ranked list of permits ordered by risk and urgency.
get_portfolio_action_plan_resourceGet today's prioritized executive action tasks for the permit management team.
get_portfolio_systemic_bottlenecks_resourceGet identified cross-cutting bottlenecks, prevalence, root causes, and fixes.
get_portfolio_changes_resourceGet day-over-day changes detected across the permit portfolio.

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a clearly distinct phase of the permitting workflow: briefing (portfolio planning), intake (SOW parsing), fee estimation, code RAG search, readiness audit, AHJ response generation, and contractor compliance verification. There is no meaningful overlap in the resource or action targeted by any two tools.

Naming Consistency5/5

Every tool follows a consistent verb_noun snake_case pattern (get_daily_manager_briefing, intake_project_scope, estimate_permit_fees_and_sla, check_permit_readiness, etc.). No mixing of conventions or verb styles, making the set highly predictable.

Tool Count5/5

Seven tools is well-scoped for a permit-management assistant, with each tool earning its place by covering a discrete lifecycle step. There is no redundancy or filler.

Completeness4/5

The surface comprehensively covers the pre-submission lifecycle (intake, fees, code search, readiness, response, compliance, briefing), with a sensible human-in-the-loop gate. However, there is no explicit permit-list/create/update/status tracking or submission tool, so agents cannot persist or advance permit state directly.

Maintenance

ActivityMaintained
ResponsivenessNo issues