Find_Nearby_Reported_Safety_Issues

The Find_Nearby_Reported_Safety_Issues tool is a custom MCP wrapper around an ArcGIS Geoprocessing Service that exposes two synchronous geoprocessing tasks—one for finding pedestrian-reported safety issues in the DC Metro area, and one for querying proposed development-project applications in the state of Delaware. The MCP tool itself is not directly invokable; instead, callers invoke a specific task on the underlying GPServer.


Tool Name

Find_Nearby_Reported_Safety_Issues


Tool Alias

Find Nearby Reported Safety Issues


Objective

Run a synchronous geoprocessing task hosted on the Find_Nearby_Reported_Safety_Issues GPServer—either Find Nearby Reported Safety Issues or Query Development Project Applications—after first inspecting the task's schema with get_gp_task_definition.


Description

Find_Nearby_Reported_Safety_Issues represents a synchronous ArcGIS Geoprocessing Service Web Tool. The tool itself is not an MCP-invokable operation in its own right. Instead, it groups one or more individual geoprocessing tasks that the agent can invoke. Each task has its own name, description, and input/output schema.

Important: call get_gp_task_definition first

Before invoking any task on this GPServer, the agent must first call Get GP Task Definition to retrieve the specific task's input and output schema. To prove that this happened, the invocation must include inputSchemaNonce — the name of any field defined in the retrieved input schema. Calling this tool without first calling get_gp_task_definition is treated as a failed run.

Available tasks

This GPServer exposes two tasks. Use the corresponding URL as taskUrl when invoking the tool.

Find Nearby Reported Safety Issues

https://mcpbeta.webgistesting.net/server/rest/services/Find_Nearby_Reported_Safety_Issues/GPServer/Find%20Nearby%20Reported%20Safety%20Issues

Performs a spatial query of pedestrian-reported safety issues (Vision Zero) along roadways in the DC Metro area, near 1–3 geocodeable addresses or points of interest. Returns up to 100 results per location.

Inputs:

  • buffer_distance (required) — distance to apply around each location.
  • buffer_distance_units (required) — supported categories include metric (esriMillimetersesriKilometers), US/statute (esriInchesesriMiles), international (esriIntInchesesriIntMiles), US Survey (esriUSSurveyInchesesriUSSurveyMiles), and nautical (esriNauticalMiles). Prefer metric or US/statute when possible.
  • where (optional) — a SQL WHERE clause for additional attribute filtering. Only specify this when you already know the layer's fields and example values.
  • address_or_poi_1 (required) — first geocodeable address or POI.
  • address_or_poi_2 (optional) — second address or POI.
  • address_or_poi_3 (optional) — third address or POI.

Layer fields available for filtering:

  • requesttype — example values: Speeding, Stop sign running, Red light running, Poor visibility.
  • usertype — example values: Pedestrian, Biker, Car Driver.
  • comments — free-text field.

Query Development Project Applications

https://mcpbeta.webgistesting.net/server/rest/services/Find_Nearby_Reported_Safety_Issues/GPServer/Query%20Development%20Project%20Applications

Performs a spatial query of proposed (but not yet approved) development-project applications in the state of Delaware. Returns up to 1000 results.

Inputs:

  • where (optional) — SQL WHERE clause for attribute filtering.
  • x, y (optional) — point geometry for proximity filtering. If omitted, no spatial filter is applied. Provide in WGS84 unless spatial_reference is also supplied.
  • spatial_reference (optional) — only provide when also providing x/y.
  • buffer_distance (optional) — buffer to apply around the point. Only meaningful when a point is provided. Defaults to 1 mile if a point is given without an explicit buffer.

Layer fields available for filtering:

  • county — example values: New Castle County, Kent County, Sussex County.
  • r_nr — residential / non-residential indicator. Example values: r, nr, Mixed.

Invocation pattern

  1. Call Get GP Task Definition with the desired task URL.
  2. Use the returned schema to construct the task's inputs object.
  3. Invoke Find_Nearby_Reported_Safety_Issues with:
  4. taskUrl — the task URL from step 1.
  5. inputSchemaNonce — the name of any field present in the input schema returned by step 1 (proof that you fetched it).
  6. inputs — the input argument object that conforms to the task's schema.

Result-set caps

Each task caps its result set:

  • Find Nearby Reported Safety Issues100 results per location.
  • Query Development Project Applications1000 results total.

If a follow-up request adds or removes filtering criteria, re-run the tool; do not paginate by hand.

When to use

  • The client wants to find pedestrian-reported safety issues near 1–3 addresses or POIs in the DC Metro area.
  • The client wants to spatially query proposed development-project applications in Delaware.
  • The client wants to refine previous results by adjusting where / geometry / buffer-distance criteria.

When not to use

  • The client needs all records and the result set is likely to exceed the cap (100 per location for safety issues, 1000 total for development applications).
  • The client wants the result set exported as an item, published feature service, CSV, or other format.
  • The safety-issues query needs to span more than 3 addresses or POIs.
  • The agent has not yet called Get GP Task Definition for the chosen task.

Schema

The full JSON Schema definitions for the input parameters accepted by Find_Nearby_Reported_Safety_Issues and the output payload it returns are provided as separate files alongside this document.

Input schema

The input schema describes the three required parameters: taskUrl (the fully qualified GPServer task URL), inputSchemaNonce (the proof-of-schema-fetch field name), and inputs (the task-specific input arguments).

Download or view FindNearbyReportedSafetyIssuesToolInputSchema.json

Output schema

The output schema describes the response object: a single results object whose properties depend on which task was invoked. Use get_gp_task_definition to learn each task's specific output shape.

Download or view FindNearbyReportedSafetyIssuesToolOutputSchema.json


Sample prompts to test the tool

Send any of the prompts below to your MCP-compatible AI client to verify that Find_Nearby_Reported_Safety_Issues is working correctly. The prompts are grouped by task—the Find Nearby Reported Safety Issues task targets pedestrian-reported safety issues in the DC Metro area, while the Query Development Project Applications task targets proposed (but not yet approved) development-project applications in the state of Delaware.

Find Nearby Reported Safety Issues — DC Metro area

  • Find all reported safety issues within 500 meters of the White House.
  • Are there any reported pedestrian safety issues within 1500 feet of Union Station DC or the National Mall?
  • Find all reported safety issues within 0.5 miles of Lincoln Memorial, Marie Reed Elementary School DC, or Dupont Circle.
  • Show me speeding-related safety reports within 1 kilometer of Georgetown University.
  • Find safety issues reported by bikers within 800 meters of Columbia Heights Metro Station or 14th Street and U Street NW, DC.
  • Near Eastern Market DC, H Street NE, or Capitol Hill, find all red light running or stop sign running issues reported by pedestrians or bikers within 600 feet.
  • Are there any poor visibility safety complaints within 1 mile of Reagan National Airport?
  • Find safety issues within 500 feet of the Lincoln Memorial, Dupont Circle, Capitol Building, and the Kennedy Center.

Query Development Project Applications — Delaware

  • Show me all proposed mixed-use development projects in Delaware.
  • Which proposed development projects are near Wilmington, Delaware?
  • Which proposed developments are within 2 miles of Wilmington, Delaware?
  • List all proposed development projects in Sussex County, Delaware.
  • Show me proposed mixed-use developments in Kent County within 3 miles of Dover, Delaware.
  • Find proposed residential-only developments within 5 kilometers of Rehoboth Beach, Delaware.
  • Are there any proposed non-residential development projects in Kent County, Delaware?
  • List all proposed development project applications in Delaware.

Reminder Each prompt above ultimately invokes one of the two tasks on this GPServer. Before submitting, the agent must first call Get GP Task Definition for the chosen task to retrieve its input schema. The fourth prompt in the safety-issues set—Show me speeding-related safety reports…—and the sixth prompt—…red light running or stop sign running issues reported by pedestrians or bikers…—exercise attribute filtering on the requesttype and usertype fields, which require knowledge of the field names returned by the task schema.