Skip to main content
Glama
Galax-ai
by Galax-ai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAPBOX_TOKENNoMapbox API token for geocoding
READYPERMIT_API_KEYNoReadyPermit API key for full report data (coming soon)

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_propertyA

Get instant zoning analysis, buildability assessment, and development constraints for any U.S. property address. Returns zoning designation, key constraints, and a link to the full Buildability Report.

check_adu_eligibilityA

Check if a property is eligible for an ADU (Accessory Dwelling Unit) - backyard cottage, garage conversion, or addition.

check_flood_riskA

Check FEMA flood zone status and environmental risk for a U.S. property. Covers flood hazard areas, EPA contamination, wildfire zones.

compare_parcelsA

Compare multiple U.S. properties side-by-side for zoning, buildability, and risk. Ideal for investors screening deals.

what_can_i_buildA

Answer 'What can I build on this property?' - covers ADUs, expansions, garage conversions, new construction, and permitted uses.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation4/5

The tools are mostly distinct, with each focusing on a specific aspect of property analysis (zoning, ADU eligibility, flood risk, comparison, and buildability). However, 'analyze_property' and 'what_can_i_build' have some overlap, as both address buildability and development constraints, which could cause minor confusion for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., analyze_property, check_adu_eligibility, check_flood_risk, compare_parcels, what_can_i_build). The naming is clear and predictable, with no deviations in style or convention.

Tool Count5/5

With 5 tools, the set is well-scoped for a property analysis server. Each tool serves a distinct purpose related to real estate development, and the count is neither too sparse nor overwhelming, fitting typical expectations for a focused domain.

Completeness4/5

The tool surface covers key aspects of property analysis, including zoning, ADU eligibility, flood risk, and buildability, with a useful comparison tool. A minor gap exists in lacking direct tools for permit application or cost estimation, but core workflows are well-supported for the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues