AcreLens
Server Details
US land due-diligence MCP server. Returns structured reports covering solar potential, groundwater depth, flood zones, building codes, and county regulations for any US property address. Mode-aware across off-grid, rural residential, recreational, and investment use cases. 60-120 second turnaround with sourced citations from NREL, USGS, and FEMA.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 5 of 5 tools scored.
Each tool targets a clearly distinct purpose: analyze_land for full property analysis, compare_properties for batch comparison, get_land_quick_score for quick screening, get_solar_potential for solar estimates, and get_state_land_profile for state-level context. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: analyze_land, compare_properties, get_land_quick_score, get_solar_potential, get_state_land_profile. Naming is uniform and predictable.
5 tools is well-scoped for the land analysis domain. Each tool provides a distinct, necessary function without redundancy. The count is appropriate and not excessive.
The tool set covers core workflows: full analysis, comparison, quick screening, solar potential, and state context. Minor gaps exist (e.g., water access, soil data, or zoning details) but these are not essential for typical use cases.
Available Tools
5 toolsanalyze_landInspect
Generates a comprehensive land analysis report for a US property through one of four analytical lenses: off_grid, rural_residential, recreational, or investment. Call this when the user asks for a full analysis of a specific property. If the user's intent is unclear, ask which mode to use before calling. Returns a report ID and poll URL — the final structured report (scores, confidence ratings, narrative summary, source citations) is delivered asynchronously via polling or webhook. Consumes one analysis credit from your AcreLens account.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude (skip geocoding if provided). | |
| lng | No | Longitude (skip geocoding if provided). | |
| mode | Yes | Analysis lens: off_grid, rural_residential, recreational, or investment. | |
| state | Yes | 2-letter US state code (e.g. "NM"). | |
| county | No | County name (recommended for better regulation research). | |
| acreage | No | Total acreage of the parcel. | |
| address | Yes | Full street address of the US property (e.g. "123 Cabin Rd, Taos, NM"). |
Output Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | The analysis lens that was applied (echoed from the request). |
| status | Yes | Report status. Initially "authorized" or "processing"; transitions to "completed" or "failed" once analysis finishes. |
| poll_url | Yes | Absolute URL to GET the report. Returns 202 while processing, 200 with full body once completed. |
| report_id | Yes | Unique ID for the report. Use this with the poll URL to retrieve the final structured report. |
| estimated_completion_seconds | Yes | Approximate seconds until the report is ready. Use as a hint for when to first poll. |
compare_propertiesInspect
Compare 2–5 US properties side by side using the same analysis mode. Call this when the user is evaluating multiple parcels or listings and wants a comparative view. Kicks off the analyses asynchronously and returns a batch ID plus one report ID per property (in input order) to poll — scored results arrive via polling or the batch webhook, not inline. Consumes one analysis credit per property from your AcreLens account.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | Analysis lens to apply to every property. | |
| properties | Yes | Array of 2–5 properties to compare. |
Output Schema
| Name | Required | Description |
|---|---|---|
| status | Yes | Batch status. Initially "processing"; transitions to "completed" once all per-property reports terminate. |
| batch_id | Yes | Unique batch ID grouping the report jobs created by this call. |
| report_ids | Yes | Per-property report IDs in the same order as the input properties array. Poll each individually or wait for the batch.completed webhook. |
get_land_quick_scoreInspect
Get a fast suitability score (0-100) for a US property without generating a full report. Call this when the user wants a quick go/no-go assessment or an initial screening before committing to a full analysis. Returns a single score with confidence level and one-sentence rationale. Consumes a partial (0.25) analysis credit from your AcreLens account.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | Analysis lens: off_grid, rural_residential, recreational, or investment. | |
| state | Yes | 2-letter US state code (e.g. "NM"). | |
| address | Yes | Full street address of the US property. |
Output Schema
| Name | Required | Description |
|---|---|---|
| score | Yes | Overall suitability score 0-100. Null while still processing. |
| status | Yes | "completed" when the score is ready; "processing" if the poll timed out and the caller should retry the report later. |
| summary | Yes | One-sentence rationale for the score. Null while still processing or if no summary was generated. |
| report_id | Yes | Unique ID for the underlying quick-mode report. |
| confidence | Yes | Aggregate confidence level derived from per-category confidences. Null while still processing. |
get_solar_potentialRead-onlyIdempotentInspect
Estimate solar energy production potential for a US address using NREL PVWatts data. Call this when the user asks about solar power viability, off-grid energy, or panel sizing. Returns estimated annual production and a typical installed-cost bracket for the system size you specify (default 5 kW).
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude of the location. | |
| lng | No | Longitude of the location. | |
| address | No | US street address (used for geocoding fallback). | |
| system_size_kw | No | System size in kilowatts (default 5). |
Output Schema
| Name | Required | Description |
|---|---|---|
| latitude | Yes | Latitude used for the calculation. Will be the resolved geocoded value if address was provided instead of lat/lng. |
| longitude | Yes | Longitude used for the calculation. Will be the resolved geocoded value if address was provided instead of lat/lng. |
| annual_kwh | Yes | Estimated annual AC electricity production in kilowatt-hours, from NREL PVWatts. |
| cost_bracket | Yes | Typical installed-cost range (USD) for a system of this size. Indicative only; varies by region and installer. |
| system_size_kw | Yes | System nameplate capacity in kilowatts (echoed from the request, default 5). |
get_state_land_profileRead-onlyIdempotentInspect
Retrieve state-level land intelligence data covering regulation, climate, solar potential, water access, and building codes. Call this when the user wants general context about a US state before drilling into a specific property. Returns structured multi-mode profiles.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Optional mode filter. If omitted, returns all 4 modes. | |
| state_code | Yes | 2-letter US state code (e.g. "NM"). |
Output Schema
| Name | Required | Description |
|---|---|---|
| modes | Yes | Per-mode profile data, keyed by mode name (off_grid, rural_residential, recreational, investment). Contains the requested mode if a filter was provided, otherwise all four. |
| state_code | Yes | 2-letter US state code echoed from the request. |
| shared_facts | No | Cross-mode state-level facts (statute citations, agency names, etc.) that apply across all modes. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!