Skip to main content
Glama
Sign In

Listing Location Toolkit

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Street crime nearby (UK)

crime_nearby
Read-onlyIdempotent

Crimes and anti-social behaviour recorded by police within 1 mile of an address in the latest published month (data.police.uk, England, Wales and Northern Ireland), by type, with the count within 400 m. Central London falls back to a quarter mile. US: says plainly that no free national crime data by address exists and where to look.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crime_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees (use with lon instead of address).
lonNoLongitude in decimal degrees.
addressNoStreet address with town and ZIP or postcode, e.g. "7090 State Highway 80, Cooperstown, NY 13326" or "Ambleside LA22 9BB". Not needed when lat and lon are given.
countryNoOptional hint for the address lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, yet the description adds substantive behavior: data recency (latest published month), a hard geographic coverage boundary, a radius fallback for Central London, and the important fact that US addresses return an explanatory statement rather than data instead of erroring.

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?

One dense, front-loaded paragraph with no filler. The trailing US sentence is telegraphic ('says plainly that...') and slightly awkward, but it is short and carries real information.

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

Completeness4/5

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

With no output schema, the description does the necessary work by describing the return shape (crimes by type with a 400 m count), the time window, and the geographic limits. The relationship between the 1 mile radius and the '400 m count' is left a little unclear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter is described, so the baseline is 3. The description adds only indirect meaning, clarifying which countries the address path actually works for, but says nothing about how lat/lon versus address are prioritized beyond what the schema already states.

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+resource (police-recorded crimes and anti-social behaviour near an address) with concrete scope: 1 mile radius, latest published month, data.police.uk, England/Wales/Northern Ireland. This is clearly distinguishable from siblings like schools_nearby, flood_risk, or area_profile.

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

Usage Guidelines3/5

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

Usage is implied by the name and the data description, and the US clause hints at what happens outside the covered geography, but there is no explicit when-to-use/when-not guidance or named alternative for US crime questions beyond a vague 'where to look'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Listing Location Toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources