Skip to main content
Glama

Get matching project records

get_projects
Read-onlyIdempotent

Project records matching a filter set: name, headline, summary, status, place, parties without emails, and size. Address, city, county, countyFips, state, and postalCode are separate fields. Each record carries latitude and longitude when the project is mapped; locationPrecision says how exact the point is (address or parcel is the site, city or county is the centre of that place). Same filters as the Boardwalk map and as count_projects, including q. limit is required (max 25). A review past 250 records is past one chat page; create_export queues a CSV of the full match set. Each new or changed record counts toward 100,000 export records a month on County, State, and National plans. An unchanged record already delivered does not. Find Contact Info does not use credits on this call. On API Only and the trial, costs 1 credit per new or changed record. Absent fields were not in the filing. get_project reads one id, including filing text. dateRange="all" searches the whole corpus; the default is last_1_year. count_projects returns the same count without records. Returns private leads by default, same as the map. leadTypes (["private","public"] for public-sector projects; "private_minor" or "public_minor" for small jobs) widens that set. Ground-up versus renovation is constructionTypes. Standard and full records carry leadType and stage; compact omits them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": "<limit>"
    },
    "name": "get_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSame as the Boardwalk map search box. Project name, developer, or words from the filing — e.g. "Ivory apartments Salt Lake". Combine with Region, Type, Acres, and Date Range.
idsNoAlias of projectIds.
bboxNoBounding box as {north,south,east,west} or west,south,east,north.
cityNoAlias of cities.
sortNomeetingDate, dateAdded, lastUpdated, dataRichness, totalUnitCount, acreage — or product aliases meeting_date_newest, created_at_newest, units_highest, acres_highest. "Recently added" is dateAdded (newest first by default). Do not send suggested (map-only).
typeNoAlias of propertyTypes.
limitYesRequired. Number of records to return, 1-25. Each new or changed record counts toward 100,000 export records a month. An unchanged record already delivered does not.
orderNo
stateNoAlias of states.
boundsNoAlias of bbox.
circleNoRadius search {lat, lng, radiusMeters}. radiusMeters is 100–500000 (meters, not miles).
citiesNoRegion: city ids or names. Narrows states the same way counties do.
cityIdNo
countyNoAlias of counties.
dateToNo
inSfhaNoAlias of inFemaFloodZone.
offsetNo
searchNoAlias of q.
statesNoRegion: state ids, names, or abbreviations. Resolve names via list_locations if unsure.
statusNoEntitlement status, whoever gave it. Tokens from get_reference facet=statuses. To ask who gave it as well, use entitlementStatus.
cityIdsNo
includeNoPass "contacts" with projectIds to read stored contacts after enrichment. get_projects uses cachedOnly=true; it never starts a live lookup. Use create_enrichment to find new contact info.
polygonNoGeoJSON ring [[lng,lat],…].
stateIdNo
subtypeNoAlias of propertySubtypes.
countiesNoRegion: county ids or names. When using names, send states separately (e.g. states:["UT"], counties:["Davis"]). Do not put "County, ST" in one value. Ambiguous names are refused even on a single-state plan. Naming a county or city narrows the search to it: states sent with it are not searched in full, and the response warns geography_narrowed_to_smallest_scope.
countyIdNo
dateFromNoDate Range lower bound, YYYY-MM or YYYY-MM-DD
stateIdsNoAlias of states.
countyIdsNo
dateRangeNoDate Range chip. Defaults to last_1_year. Pass "all" for the whole corpus.
leadTypesNoLead types to include. Default ["private"] — private development only, same as the map. Widen it when they ask: ["private","public"] adds public-sector projects (schools, roads, utilities, civic facilities); ["private","private_minor"] adds small private jobs (single lots, tenant improvements, small additions); "public_minor" adds small public jobs. Infrastructure and Institutional/Public projects are mostly government-owned, so add "public" whenever you filter for them (propertyTypes Infrastructure or Institutional/Public, or constructionTypes infrastructure). Always keep "private" in the list — the API adds it back if you drop it. Standard and full records carry leadType and stage; compact omits them.
acreageMaxNoAcres maximum.
acreageMinNoAcres minimum. “Projects over 2 acres” → acreageMin=2.
assetClassNoAlias of assetClasses.
lotSizeMaxNoAlias — prefer acreageMax when they said acres.
lotSizeMinNoAlias — prefer acreageMin when they said acres.
maxCreditsNoExplicit acknowledgement of the maximum credits this call may spend. Required once the projected cost passes the free floor; the tool refuses and charges nothing without it.
projectIdsNoExact record ids to re-read, at most 100. Owned unchanged records are free. On count_projects this must be the only filter.
projectNameNo
assetClassesNoBuilding type class (3rd level: Gas Stations, Apartment Building, …).
deliveryModeNo
excludeSavedNoWhen true, hide projects already on a saved list this account can see.
projectSizesNoProject Size: large, medium, or small. “Large projects” → large.
requestTypesNoApplication type, what they asked for. Early: annexation, general_plan_amendment, rezone, planned_unit_development, concept_plan, project_plan. Middle: conditional_use_permit, special_use_permit, variance, development_agreement, preliminary_plat, subdivision_plat. Late: site_plan_approval, design_review, final_plat. Early types are the first sign of a project; late ones mean it is close to building.
unitCountMaxNoAlias of totalUnitCountMax.
unitCountMinNoAlias of totalUnitCountMin.
civicSubtypesNoAlias of governmentDecisionSubtypes.
decisionTypesNo
developerNameNo
lastUpdatedToNo
meetingDateToNo
propertyTypesNoBuilding type from get_project_types (Commercial, Residential, …). Alias: type.
excludeAlertIdNoSubtract every project any delivery of this alert (alr_…) has ever materialised.
excludeSubtypeNoAlias of excludePropertySubtypes.
lotSizeSqftMaxNoAlias of lotSizeMax.
lotSizeSqftMinNoAlias of lotSizeMin.
showAllRecordsNoAlias of includeGovernmentDecisions.
inFemaFloodZoneNoFEMA flood zone overlay.
lastUpdatedFromNo
meetingDateFromNo
applicationTypesNoAlias of requestTypes.
parkingSpacesMaxNo
parkingSpacesMinNo
propertySubtypesNoMore-specific building type (2nd level).
squareFootageMaxNoBuilding square footage maximum.
squareFootageMinNoBuilding square footage minimum.
civicAssetClassesNoAlias of governmentDecisionAssetClasses.
constructionTypesNoConstruction type: new_building, renovation, addition, infrastructure. "Renovation or addition" is renovation plus addition, so send both.
entitlementStatusNoEntitlement status by who gave it, as "<bodyGroup>:<status>" pairs, e.g. ["council:approved","planning:recommended_for_approval"]. A pair matches the project's newest decision. Body groups: council (city council or county board), planning (planning commission), boards (appeals and review boards), staff (planning staff), other (another body). Statuses: approved, denied, recommended_for_approval, recommended_for_denial, continued, pending, withdrawn. "Approved by the planning commission" → ["planning:approved"]. get_reference facet=entitlementStatus lists both halves.
excludeAssetClassNoAlias of excludeAssetClasses.
excludeProjectIdsNoSubtract these ids from search/count (at most 100).
inOpportunityZoneNo2027 Opportunity Zone overlay (effective January 1, 2027).
taxonomyMatchModeNoHow a Building type filter matches. Default primary_or_secondary. Rarely needed.
totalUnitCountMaxNoResidential Units maximum.
totalUnitCountMinNoResidential Units minimum.
buildingStoriesMaxNo
buildingStoriesMinNo
excludeAssetClassesNoBuilding type classes to leave out.
constructionLeadOnlyNoAlias of constructionLeadsOnly.
constructionLeadsOnlyNo
constructionMagnitudesNoAlias of projectSizes.
hasConstructionDetailsNo
excludePropertySubtypesNoBuilding types to leave out (2nd level).
governmentDecisionSubtypesNoGovernment decision types. Requires includeGovernmentDecisions=true.
includeGovernmentDecisionsNoInclude non-real-estate government decisions (ordinances, budgets). Default false. Pass true only when they ask for them. Deprecated: still accepted, but leadTypes is how the served set is widened now — prefer leadTypes: ["private","public"] for public-sector work.
governmentDecisionAssetClassesNoGovernment decision classes. Requires includeGovernmentDecisions=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedInput schema / properties / constructionTypes / description
      Previous value: -"Construction Type: new_building, infrastructure, renovation, site_work, demolition_only."New value: +"Construction type: new_building, renovation, addition, infrastructure. \"Renovation or addition\" is renovation plus addition, so send both."
    • removedInput schema / properties / decisionBodies
      Removed value: -{
      -  "$ref": "#/properties/states",
      -  "description": "Hearing body from get_reference (Planning Commission, City Council, …)."
      -}
    • addedInput schema / properties / entitlementStatus
      Added value: +{
      +  "$ref": "#/properties/states",
      +  "description": "Entitlement status by who gave it, as \"<bodyGroup>:<status>\" pairs, e.g. [\"council:approved\",\"planning:recommended_for_approval\"]. A pair matches the project's newest decision. Body groups: council (city council or county board), planning (planning commission), boards (appeals and review boards), staff (planning staff), other (another body). Statuses: approved, denied, recommended_for_approval, recommended_for_denial, continued, pending, withdrawn. \"Approved by the planning commission\" → [\"planning:approved\"]. get_reference facet=entitlementStatus lists both halves."
      +}
    • changedInput schema / properties / governmentDecisionAssetClasses / description
      Previous value: -"Govt. Decision classes. Requires includeGovernmentDecisions=true."New value: +"Government decision classes. Requires includeGovernmentDecisions=true."
    • changedInput schema / properties / governmentDecisionSubtypes / description
      Previous value: -"Govt. Decision types. Requires includeGovernmentDecisions=true."New value: +"Government decision types. Requires includeGovernmentDecisions=true."
    • changedInput schema / properties / includeGovernmentDecisions / description
      Previous value: -"Show Non-Real Estate Govt. Decisions. Default false, same as the map. Pass true only when they ask for Govt. Decisions. Deprecated: still accepted, but leadTypes is how the served set is widened now — prefer leadTypes: [\"private\",\"public\"] for public-sector work."New value: +"Include non-real-estate government decisions (ordinances, budgets). Default false. Pass true only when they ask for them. Deprecated: still accepted, but leadTypes is how the served set is widened now — prefer leadTypes: [\"private\",\"public\"] for public-sector work."
    • changedInput schema / properties / leadTypes / description
      Previous value: -"Lead types to include. Default [\"private\"] — private development only, same as the map. Widen it when they ask: [\"private\",\"public\"] adds public-sector projects (schools, roads, utilities, civic facilities); [\"private\",\"private_minor\"] adds small private jobs (single lots, tenant improvements, small additions); \"public_minor\" adds small public jobs. Always keep \"private\" in the list — the API adds it back if you drop it. Standard and full records carry leadType and stage; compact omits them."New value: +"Lead types to include. Default [\"private\"] — private development only, same as the map. Widen it when they ask: [\"private\",\"public\"] adds public-sector projects (schools, roads, utilities, civic facilities); [\"private\",\"private_minor\"] adds small private jobs (single lots, tenant improvements, small additions); \"public_minor\" adds small public jobs. Infrastructure and Institutional/Public projects are mostly government-owned, so add \"public\" whenever you filter for them (propertyTypes Infrastructure or Institutional/Public, or constructionTypes infrastructure). Always keep \"private\" in the list — the API adds it back if you drop it. Standard and full records carry leadType and stage; compact omits them."
    • changedInput schema / properties / requestTypes / description
      Previous value: -"Application Type — what they asked for (rezone, site plan, …)."New value: +"Application type, what they asked for. Early: annexation, general_plan_amendment, rezone, planned_unit_development, concept_plan, project_plan. Middle: conditional_use_permit, special_use_permit, variance, development_agreement, preliminary_plat, subdivision_plat. Late: site_plan_approval, design_review, final_plat. Early types are the first sign of a project; late ones mean it is close to building."
    • removedInput schema / properties / requiresZoningChange
      Removed value: -{
      -  "description": "Requires Zoning Change — map More toggle.",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / sort / description
      Previous value: -"meetingDate, lastUpdated, dataRichness, totalUnitCount, acreage — or product aliases meeting_date_newest, units_highest, acres_highest. Do not send suggested (map-only)."New value: +"meetingDate, dateAdded, lastUpdated, dataRichness, totalUnitCount, acreage — or product aliases meeting_date_newest, created_at_newest, units_highest, acres_highest. \"Recently added\" is dateAdded (newest first by default). Do not send suggested (map-only)."
    • changedInput schema / properties / squareFootageMax / description
      Previous value: -"Commercial Square Footage maximum."New value: +"Building square footage maximum."
    • changedInput schema / properties / squareFootageMin / description
      Previous value: -"Commercial Square Footage minimum."New value: +"Building square footage minimum."
    • changedInput schema / properties / status / description
      Previous value: -"Entitlement Status tokens from get_reference facet=statuses."New value: +"Entitlement status, whoever gave it. Tokens from get_reference facet=statuses. To ask who gave it as well, use entitlementStatus."
    • removedInput schema / properties / statusCombos
      Removed value: -{
      -  "$ref": "#/properties/states",
      -  "description": "Entitlement Status as \"City Council|approved\". Prefer this over inventing tokens."
      -}
    • removedInput schema / properties / statusSelection
      Removed value: -{
      -  "$ref": "#/properties/states",
      -  "description": "Alias of status."
      -}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive), and the description layers on genuinely non-obvious behavior: credit accounting (100,000 export records/month on County/State/National, 1 credit per new or changed record on API Only and trial, unchanged redelivered records free), the maxCredits refusal path, and the fact that Find Contact Info costs nothing here. It also discloses result semantics not visible in annotations (private leads by default, absent fields mean 'not in the filing').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and largely earns its place, but it is delivered as one undifferentiated block that jumps from return fields to billing to sibling routing to lead-type defaults without headings or bullets. For an 87-parameter tool some length is unavoidable, yet the billing and credit sentences could be consolidated and placed after the core selection guidance instead of mid-paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps up by describing the returned record (fields, lat/long, locationPrecision meaning, leadType and stage present in standard/full but omitted in compact) and by explaining cost and refusal behavior. Remaining gaps are minor: the pagination/offset interaction is only hinted at via 'past one chat page', and sort defaults are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% across 87 parameters, so the schema carries most of the load, but the description adds cross-tool parity information ('same filters as the Boardwalk map and as count_projects, including q') that an agent cannot infer from the schema alone. It also reinforces the required limit ceiling (max 25) and the default dateRange behavior, though several of these repeat schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause states a specific verb and resource ('Project records matching a filter set') and immediately enumerates the fields carried, so an agent knows exactly what shape of data comes back. It also distinguishes itself explicitly from get_project ('reads one id, including filing text') and count_projects ('returns the same count without records').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names concrete routing conditions: use create_export for a CSV of the full match set past 250 records, use get_project for a single id with filing text, use count_projects when only a count is needed. It also states trigger conditions for widening results (leadTypes for public-sector or minor jobs, 'add public whenever you filter for Infrastructure or Institutional/Public').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources