Skip to main content
Glama

Search UK Police Outcomes

ukcrime_search_outcomes
Read-onlyIdempotent

List the police outcomes recorded in one month inside an area — a point with a 1-mile radius, a polygon, a location_id, or a neighbourhood — for crimes recorded that month or any earlier one. Returns the total, counts by outcome and by the month each crime was recorded, and a page of outcomes, each with its crime and persistent_id. Use it for what police resolved in a month; ukcrime_search_crimes gives the latest outcome of the crimes recorded in a month instead. Court results are not published; the result says when a force publishes no outcomes.

Input Schema

TableJSON 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), or 'neighbourhood' (force and neighbourhood_id). An area field the chosen area does not use is rejected.
forceNoFor area 'neighbourhood', with neighbourhood_id: a force 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.
limitNoOutcomes on this page, 1–200. Default 20.
monthNoMonth as YYYY-MM. 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.
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.
categoryNoCount only outcomes for crimes in this category: a slug such as 'burglary' or a display name such as 'Violence and sexual offences'; case-insensitive, and spaces, underscores and hyphens match each other ('vehicle_crime' finds 'vehicle-crime'). Omitted or 'all-crime': every category. ukcrime_list_reference topic 'categories' lists them.
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. Case-sensitive; only trimmed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoPage limit applied.
areaNoThe area as the server searched it.
errorNoPresent when the call failed. Absent on success.
monthNoThe month searched — when the outcomes were recorded — YYYY-MM.
shownNoRows on this page.
totalNoOutcomes matched, after the category filter.
noticeNoDefaulted month, coverage gaps, why a result is empty, and how to page on.
categoryNoThe crime category counted; absent when every category was (no category, or 'all-crime').
outcomesNoThis page of matched outcomes, sorted by the crime's month, newest first, then crime id.
data_noteNoWhat these records can and cannot say; read it first.
truncatedNoTrue when more rows remain after this page.
by_outcomeNoMatched outcomes by outcome, most first.
attributionNoOpen Government Licence attribution.
next_offsetNoPass as offset for the next page; absent on the last page.
by_crime_monthNoMatched outcomes by the month their crime was recorded, newest first.
unfiltered_totalNoOutcomes recorded in the area and month before the category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world behavior, so the bar is lower; the description still adds non-obvious traits — the temporal quirk that outcomes cover crimes recorded that month or earlier, the suppress-the-result behavior when a force publishes no outcomes, and the absence of court results.

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?

Three dense sentences, front-loaded with scope, then routing, then caveats. Every clause carries information, though the first sentence is long and would read better split, which keeps it from a 5.

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?

Output schema exists, so return-value detail is optional, yet the description still sketches the payload (total, per-outcome and per-recorded-month counts, a page with crime and persistent_id). With 11 params fully documented in schema and annotations covering safety, nothing needed for a correct call 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 baseline is 3. The description goes further by naming all four area modes and clarifying that the outcome rows are for crimes recorded that month or any earlier one — a semantic the schema does not convey.

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 and resource (list police outcomes) plus the scope constraint (one month, inside an area) and enumerates the four area modes. It explicitly contrasts itself with ukcrime_search_crimes, so an agent can separate them without opening either 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?

Includes a direct routing rule: use this for what police resolved in a month, use ukcrime_search_crimes for the latest outcome of crimes recorded in a month. It also warns that court results are never published and that a force may report no outcomes, which sets correct expectations before invoking.

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.