Skip to main content
Glama

Search UK Police Stop and Search

ukcrime_search_stops
Read-onlyIdempotent

Search police stop and search records for one month, or with month_from a range of up to 12 months, inside an area — a point with a 1-mile radius, a polygon, a location_id from an earlier result, or a police neighbourhood — or across a whole force with area 'force', which includes stops the force could not place. Returns the total and counts by search type, self-defined and officer-defined ethnicity, outcome, object of search, legislation, age range, gender, whether the outcome was linked to the object of search, and whether more than outer clothing was removed, each month's total for a range, and a page of stops. filters narrow the counts and the page together, so filtering one field and reading another's breakdown gives a cross-tab. Forces skip months and some publish none; the result names each force it finds for the area that did not publish, with the months it skipped.

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": {
      "area": "<area>"
    },
    "name": "ukcrime_search_stops"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, WGS84 decimal degrees, for area 'point'.
lngNoLongitude, WGS84 decimal degrees, for area 'point'.
areaYesArea to search: 'point' (lat and lng; a 1-mile radius), 'polygon' (polygon), 'location' (location_id), 'neighbourhood' (force and neighbourhood_id), or 'force' (force alone: every stop the force published for the month or range, placed or not). An area field the chosen area does not use is rejected.
forceNoForce id such as 'leicestershire', or its name such as 'Leicestershire Police' (ukcrime_list_reference topic 'forces' lists both); case-insensitive, spaces, underscores and hyphens match each other, '&' matches 'and', and a trailing 'Police', 'Police Service' or 'Constabulary' is optional. For area 'neighbourhood' (with neighbourhood_id) and 'force' (alone), where 'btp' (British Transport Police) is also accepted.
limitNoRequested stops on this page, 1–10,000; applied cap is at most 200. Default 15.
monthNoMonth as YYYY-MM, or the last month of the range with month_from. Omitted: the latest published month, echoed as month in the result.
offsetNoRows to skip before this page; pass next_offset from the previous result. Default 0.
filtersNoUp to 8 filters, all of which a stop must match; they narrow the counts and the page together. Fields: type, self_defined_ethnicity, officer_defined_ethnicity, outcome, object_of_search, legislation, age_range, gender, outcome_linked_to_object_of_search, removal_of_more_than_outer_clothing.
polygonNoFor area 'polygon': 3–2,500 vertices as { lat, lng } objects, or the string 'lat,lng:lat,lng:…'. The ring closes itself (the last vertex joins the first). [lng, lat] pairs are not accepted.
month_fromNoFirst month of a range, YYYY-MM, searched through month — up to 12 months, with a total for each in by_month. Omitted: month alone.
location_idNoFor area 'location': location.location_id from an earlier result — one anonymised map point.
neighbourhood_idNoFor area 'neighbourhood', with force: a neighbourhood id from ukcrime_list_reference topic 'neighbourhoods', or from ukcrime_find_neighbourhood for a point. Exact spelling first; after a miss, a unique case-insensitive catalog match is retried.

Output Schema

NameRequiredDescriptionDefault
capNoPage limit applied.
areaNoThe area as the server searched it.
errorNoPresent when the call failed. Absent on success.
monthNoThe month searched, or the last month of the range, YYYY-MM.
shownNoRows on this page.
stopsNoThis page of matched stops, oldest first, then by location_id.
totalNoStops matched after filters, over the month or range.
noticeNoDefaulted month, coverage gaps, why a result is empty, and how to page on.
by_typeNoMatched stops by search type, most first.
filtersNoFilters applied, case-insensitively; empty when none.
by_monthNoStops matched in each month of the range, oldest first; their totals sum to total. Present only when month_from was given.
unplacedNoMatched stops with no location — the force's unplaced stops, for area 'force'.
by_genderNoMatched stops by gender, most first.
data_noteNoWhat these records can and cannot say; read it first.
truncatedNoTrue when more rows remain after this page.
by_outcomeNoMatched stops by outcome, most first; '(not recorded)' is often the largest.
month_fromNoFirst month of the range searched, YYYY-MM; present only when month_from was given.
attributionNoOpen Government Licence attribution.
next_offsetNoPass as offset for the next page; absent on the last page.
by_age_rangeNoMatched stops by age range, most first.
by_legislationNoMatched stops by legislation, most first.
force_publishedNoWhether every force found for the area (the one it names, or each located at a point, a polygon's centre and outermost vertices, or a location's map point) published stop and search this month, or in every month of a range: false when any month was missed. Otherwise absent when no force was found, when a month has no row in the publication list, or when none of those found is missing yet a polygon point could not be looked up.
unfiltered_totalNoStops in the area over the month or range, before filters.
by_object_of_searchNoMatched stops by object of search, most first.
by_self_defined_ethnicityNoMatched stops by ethnicity as the person defined it, most first.
by_officer_defined_ethnicityNoMatched stops by ethnicity as the officer perceived it, most first.
by_outcome_linked_to_object_of_searchNoMatched stops by whether the outcome was linked to the object of search ('true', 'false' or '(not recorded)'), most first.
by_removal_of_more_than_outer_clothingNoMatched stops by whether more than outer clothing was removed ('true', 'false' or '(not recorded)' where the force sent no value, as some do for vehicle-only searches), most first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Stops on this page, 1–200. Default 15."New value: +"Requested stops on this page, 1–10,000; applied cap is at most 200. Default 15."
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +10000
    • changedInput schema / properties / neighbourhood_id / description
      Previous value: -"For area 'neighbourhood', with force: a neighbourhood id from ukcrime_list_reference topic 'neighbourhoods', or from ukcrime_find_neighbourhood for a point. Case-sensitive; only trimmed."New value: +"For area 'neighbourhood', with force: a neighbourhood id from ukcrime_list_reference topic 'neighbourhoods', or from ukcrime_find_neighbourhood for a point. Exact spelling first; after a miss, a unique case-insensitive catalog match is retried."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_area`: the area's required fields are missing, or a field it does not use is present. `month_not_published`: month or month_from is after the latest published month. `month_out_of_range`: month or month_from is before the 36-month window. `invalid_month_range`: month_from is after month, or the range spans more than 12 months. `unknown_force`: force matches no listed force id or name, or more than one, or is 'btp' on area 'neighbourhood'. `unknown_neighbourhood`: the force has no neighbourhood with this id (ids are case-sensitive). `area_too_large`: the area holds more stops than data.police.uk will answer for. `range_too_large`: the range's months hold more records than one call keeps for a range. `range_incomplete`: the months of the range could not all be fetched within the time one call allows. `upstream_unavailable`: data.police.uk is not answering. `rate_limited`: data.police.uk is rate-limiting this server for longer than this call can wait. `pacer_shed`: too many requests to data.police.uk are already queued in this server. `retry_deadline_exceeded`: data.police.uk did not answer within the time one call allows. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `ambiguous_neighbourhood`: an exact neighbourhood request misses and more than one catalog id matches without case. `invalid_area`: the area's required fields are missing, or a field it does not use is present. `month_not_published`: month or month_from is after the latest published month. `month_out_of_range`: month or month_from is before the 36-month window. `invalid_month_range`: month_from is after month, or the range spans more than 12 months. `unknown_force`: force matches no listed force id or name, or more than one, or is 'btp' on area 'neighbourhood'. `unknown_neighbourhood`: the exact neighbourhood request and any unique case-insensitive catalog match miss. `area_too_large`: the area holds more stops than data.police.uk will answer for. `range_too_large`: the range's months hold more records than one call keeps for a range. `range_incomplete`: the months of the range could not all be fetched within the time one call allows. `upstream_unavailable`: data.police.uk is not answering. `rate_limited`: data.police.uk is rate-limiting this server for longer than this call can wait. `pacer_shed`: too many requests to data.police.uk are already queued in this server. `retry_deadline_exceeded`: data.police.uk did not answer within the time one call allows. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_area",
      -  "month_not_published",
      -  "month_out_of_range",
      -  "invalid_month_range",
      -  "unknown_force",
      -  "unknown_neighbourhood",
      -  "area_too_large",
      -  "range_too_large",
      -  "range_incomplete",
      -  "upstream_unavailable",
      -  "rate_limited",
      -  "pacer_shed",
      -  "retry_deadline_exceeded"
      -]New value: +[
      +  "ambiguous_neighbourhood",
      +  "invalid_area",
      +  "month_not_published",
      +  "month_out_of_range",
      +  "invalid_month_range",
      +  "unknown_force",
      +  "unknown_neighbourhood",
      +  "area_too_large",
      +  "range_too_large",
      +  "range_incomplete",
      +  "upstream_unavailable",
      +  "rate_limited",
      +  "pacer_shed",
      +  "retry_deadline_exceeded"
      +]
    • changedOutput schema / properties / stops / items / properties / outcome / description
      Previous value: -"Outcome."New value: +"Outcome; a published false means Nothing found, while blank, null or absent is unrecorded."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/open-world, yet the description adds substantive behavioural context the annotations cannot: filters narrow counts and page together (enabling cross-tabs), and forces skip months or publish none, with the result naming each non-publishing force and its skipped months. That data-availability caveat is exactly the kind of extra disclosure this dimension rewards.

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?

Purpose and area modes are front-loaded, but it is one sprawling sentence that enumerates every breakdown field (type, ethnicity, outcome, object, legislation, age, gender, linked, outer clothing) and the filter field list, content already supplied by the output schema and filters enum. Those clauses are bloat rather than earning their place.

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

Completeness5/5

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

For a 12-parameter tool with an output schema, the description covers what is needed to call it correctly: all five area modes and their required companions, month vs month_from range behaviour, filter interaction with counts and page, and the force-publication gaps that affect result interpretation. Nothing material is missing.

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 100%, so parameters are already fully documented and the baseline is 3. The description adds cross-field semantics not in the schema — that filtering one breakdown field while reading another yields a cross-tab, and that a range produces a by_month total per month — which raises it above baseline.

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?

States a specific verb (Search) plus resource (police stop and search records) and pins down the scope: one month or a month_from range up to 12, inside a point/polygon/location_id/neighbourhood or across a whole force. An agent can distinguish this from ukcrime_search_crimes or ukcrime_search_outcomes purely from the text.

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

Usage Guidelines4/5

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

Explains the conditions under which each area mode applies (point needs lat/lng, range needs month_from, 'force' includes unplaced stops) and warns that forces skip months. It never explicitly names the sibling to use instead, so routing between it and ukcrime_search_crimes/search_outcomes is left to inference.

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.