Dallas Civic MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aboutA | Show information about this MCP server, including its name, version, data sources, license, and the original author. Always available. (via Dallas Civic MCP -- forked from Local Dallas MCP by Ed Neuhaus) |
| dallas_nws_alertsA | Active National Weather Service alerts (severe thunderstorm, tornado, flood, heat, freeze, fire weather) for a specific Dallas location. Defaults to central Dallas when no address is supplied. Returns severity, urgency, headline, description, and expiration time for every active alert covering the point. Authoritative source: National Weather Service (api.weather.gov). |
| dallas_tea_schoolsA | Look up Texas public schools and their TEA accountability ratings. Search by campus name, district, county, or city. Returns the A-F overall rating, sub-scores (Student Achievement, School Progress, Closing the Gaps), enrollment, demographics, district info, address, phone, and website. Example districts: "Dallas ISD", "Plano ISD", "Highland Park ISD". Authoritative sources: Texas Education Agency (2022-2023 ratings) and AskTED directory. Note: this does NOT map an address to its assigned schools -- attendance zones are managed by individual ISDs. |
| dallas_311A | Search City of Dallas 311 service requests (code compliance, streets, sanitation, and other non-emergency city services). Filter by request type, department, status, council district, or date range. Authoritative source: City of Dallas Open Data. |
| dallas_permitsA | Search City of Dallas building permits (new construction, remodels, electrical, mechanical, plumbing, etc). Filter by permit type, status, council district, or address. Authoritative source: City of Dallas Open Data. |
| dallas_crimeA | Search Dallas Police reported incidents (RMS data, 2014-present). Filter by offense/keyword, council district, or address -- or pass no filters for the most recent reports. Sexually-oriented offenses and records involving juveniles are excluded by the Dallas Police Department before publication, per its public-data policy. Authoritative source: City of Dallas Open Data. |
| dallas_propertyA | Look up a Dallas-area tax parcel by street name or account number: owner name, situs address, legal description, property class, and council district, from the City of Dallas GIS parcels layer (built from certified county appraisal-district data). This layer does NOT carry dollar appraised/market value or current tax bill/payment status directly, but each record includes a direct link to that parcel's county appraisal district detail page, where that information lives. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct civic dataset: weather alerts, school data, 311 service requests, permits, crime, and property. There is no functional overlap between the domain tools, and the 'about' meta-tool is clearly separated. An agent would have little trouble selecting the right tool for a query.
Domain tools consistently use a 'dallas_' prefix followed by a clear noun (e.g., dallas_crime, dallas_property). The exception is 'about', which lacks the prefix but is a common server metadata tool. Overall naming is coherent and readable with only a minor deviation.
Seven tools (six data tools plus one meta tool) are well within the ideal range for a focused civic data MCP server. Each tool adds a distinct data source and the set feels appropriately scoped—neither sparse nor bloated.
The server covers the main civic data areas expected for the City of Dallas: alerts, schools, 311, permits, crime, and property records. Some adjacent areas (e.g., traffic, transit, city budgets) are missing, and the property tool deliberately excludes appraised values, so completeness is strong but not exhaustive.