MCP Server Police UK
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_street_level_crimesB | Retrieve street-level crimes by lat/lng or custom polygon area |
| get_street_level_outcomesB | Retrieve outcomes by lat/lng, custom polygon, or location ID |
| get_crimes_at_locationB | Retrieve crimes at a specific location by ID or nearest to lat/lng |
| get_crimes_no_locationB | Retrieve crimes that could not be mapped to a location |
| get_crime_categoriesB | Retrieve valid crime categories for a given date |
| get_last_updatedA | Retrieve the date when crime data was last updated |
| get_outcomes_for_crimeC | Retrieve outcomes for a specific crime by persistent ID |
| get_list_of_forcesA | Retrieve a list of all police forces |
| get_force_detailsB | Retrieve details for a specific police force |
| get_senior_officersB | Retrieve senior officers for a specific police force |
| get_neighbourhoodsA | Retrieve a list of neighbourhoods for a specific police force |
| get_neighbourhood_detailsC | Retrieve details for a specific neighbourhood within a force |
| get_neighbourhood_boundaryB | Retrieve the boundary coordinates for a specific neighbourhood |
| get_neighbourhood_teamB | Retrieve the team members for a specific neighbourhood |
| get_neighbourhood_eventsB | Retrieve events scheduled for a specific neighbourhood |
| get_neighbourhood_prioritiesB | Retrieve policing priorities for a specific neighbourhood |
| locate_neighbourhoodA | Find the neighbourhood policing team for a given latitude and longitude |
| get_stop_searches_by_areaB | Retrieve stop and searches within a 1-mile radius or custom area |
| get_stop_searches_by_locationB | Retrieve stop and searches at a specific location by ID |
| get_stop_searches_no_locationB | Retrieve stop and searches that could not be mapped to a location |
| get_stop_searches_by_forceA | Retrieve stop and searches reported by a specific force |
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 21 tools
Most tools have distinct purposes (crimes, stops, forces, neighbourhoods), but some like get_crimes_at_location and get_street_level_crimes could be confused due to similar inputs and outputs.
All tools follow a consistent 'get_' prefix with descriptive snake_case names, e.g., get_crime_categories, get_neighbourhood_events.
21 tools is appropriate for a police data API covering forces, neighbourhoods, crimes, stop searches, and outcomes without being overwhelming.
Covers key police data aspects: forces, neighbourhoods, crimes, stop searches, outcomes, and location features. No obvious gaps for the intended domain.