mcp-livedatapro

getLocalCrimeStats

Hyperlocal street-level crime rates, safety index scores, and 12-month incident breakdowns by postcode or GPS. Use when evaluating neighborhood safety scores (0-100), crime rates vs national average, and 12-month police incident breakdowns (violent, burglary, vehicle theft) by postcode or GPS coordinates. Do not use for cybersecurity IP fraud checks (use getIpIntelligence).

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": {
      "location_query": "<location_query>"
    },
    "name": "getLocalCrimeStats"
  }
}

Input Schema

Name	Required	Description	Default
`location_query`	Yes	Postal/ZIP code, neighborhood name, or GPS coordinates (lat,lon).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / location_query / examples
```
Added value: +[
+  "E1 6AN, London"
+]
```
- addedInput schema / properties / location_query / minLength
```
Added value: +3
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / location_query / description

Previous value: -"Postcode, ZIP code, or lat,lon coordinates"New value: +"Postal/ZIP code, neighborhood name, or GPS coordinates (lat,lon)."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the data granularity, score range, comparison to national average, 12-month time window, and incident categories, but it does not state operational behavior such as read-only status, data freshness, permissions, or rate limits.

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?

The description is front-loaded and appropriately sized: what it returns, when to use it, and when not to use it. It has some repetition between the first two sentences, but the repetition adds score range, comparison context, and incident categories rather than wasting space.

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?

For a one-parameter lookup tool with no output schema, the description is largely complete: it explains the returned data categories, granularity, score range, and time window. It could be stronger by clarifying output structure or data freshness, but an agent has enough to call it correctly.

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?

The single parameter has 100% schema description coverage, so the schema already explains postal/ZIP code, neighborhood name, and GPS coordinates. The description reinforces postcode/GPS but does not add syntax or meaning beyond the schema, and it omits the neighborhood-name option documented in the schema.

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?

The description states a specific resource and scope: hyperlocal street-level crime rates, safety index scores, and 12-month incident breakdowns by postcode or GPS. It also distinguishes the tool from getIpIntelligence, making its purpose clear without needing the 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?

It explicitly says when to use the tool — evaluating neighborhood safety scores, crime rates vs national average, and police incident breakdowns — and when not to use it, naming getIpIntelligence as the alternative for IP fraud checks.

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

All mcp-livedatapro tools Inspect

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

Need Help?