Skip to main content
Glama

Queue a CSV export

create_export

Queues a CSV of every matching project: a saved alert or list with optional in-set filters, a list of projectIds, or a new search. With alertId, listId, or projectIds, the status, entitlementStatus, requestTypes, and buildingStories filters are refused: a saved set cannot answer them. Every row has Latitude, Longitude, and Location Precision columns for loading into a map. The response is a receipt, never the CSV bytes. New or changed rows count toward 100,000 export records a month on County, State, and National, and cost 1 credit each on API Only and the trial; rows already delivered unchanged are not charged again. Find Contact Info does not use credits unless include="contacts". include="contacts" runs contact lookup and costs 1 credit per project when an email, phone, or personal LinkedIn profile is found. get_export returns status and the download page. count_projects returns the match count for a new search. Send them to https://boardwalkai.com/exports to download the file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_export"
  }
}

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.
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.
listIdNoExport a named list. Alert companions are the same set as the alert. Extra filters stay inside those ids.
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.
alertIdNoExport the projects already on this alert (matches minus dismissed). Prefer this after a pull. Extra filters stay inside those ids.
cityIdsNo
includeNoPass "contacts" to run Find Contact Info on the file (monthly allowance).
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.
projectIdsNoThe ids you already have after pull or further filtering in chat. Prefer alertId/listId when the whole saved set should go in the file. At most 2500 here; larger saved sets use alertId or listId.
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.7/5.0
Behavior5/5

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

Annotations only say this is a non-readonly, non-destructive, non-idempotent write; the description adds what actually matters: the response is a receipt and never CSV bytes, rows carry Latitude/Longitude/Location Precision, unchanged rows are not re-charged, and the monthly 100,000-record cap plus per-credit costs for API Only/trial plans. The include="contacts" cost rule (1 credit per project only when an email, phone, or personal LinkedIn is found) is behavior no annotation could convey.

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

Conciseness4/5

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

Purpose and selection modes are front-loaded, then refusals, then output shape, then cost, then next-step tools — a sensible order. The billing sentences are dense and long, but each carries decision-relevant information (monthly cap, per-row credit, unchanged-row exemption) rather than restating the schema.

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?

For an 87-parameter, zero-required, no-output-schema tool, the definition covers what an agent most needs: how to select a set, which filter combinations fail, that the return is a receipt, where the file is downloaded, and which sibling to call next. It does not explain the 2500-id ceiling or how the 2500 max interacts with large saved sets, which the schema carries instead.

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 does most of the work and baseline would be 3. The description still adds value the schema cannot: the cross-parameter refusal rule for status/entitlementStatus/requestTypes/buildingStories under saved-set ids, and the credit consequence of include="contacts". It does not attempt to explain the remaining filters, which is acceptable given the schema's own 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 description opens with a specific verb and resource ("Queues a CSV of every matching project") and immediately enumerates the three selection modes: a saved alert or list, a projectIds list, or a new search. This lets an agent distinguish it from get_export (status/download) and count_projects (match count) without opening any schema.

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 gives explicit routing rules: use get_export for status and the download page, use count_projects to preview a new search's match count, and prefer alertId/listId when the whole saved set should go into the file. It also states a concrete exclusion — status, entitlementStatus, requestTypes, and buildingStories are refused when alertId, listId, or projectIds is supplied — which tells the agent when not to combine filters.

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