Skip to main content
Glama

Nearby incidents

nearby_incidents
Read-only

Police-published incident records around an address or point, newest first: what, when, block-level address, type, record type and source, typed as crimemetric.com's city pages type them. Sensitive cases come without a location. Calls (calls for service, and records that read as calls) are left out unless include_calls is true. The full list is on the Developer and Business plans. On the free plan it returns a preview instead (preview: true): the 5 newest records from the last 90 days in the 1 km grid square that contains the point, with date, type, record type and agency only, plus counts by type; sexual, domestic and juvenile cases are left out, radius, limit, dates and filters are ignored, and cursor is refused.

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": "nearby_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (default: today)
latNoLatitude
lonNoLongitude
fromNoFirst day, YYYY-MM-DD (default: 90 days before `to`)
crimeNoOnly these types: murder, rape, robbery, aggravated_assault, burglary, shoplifting, theft_from_vehicle, other_larceny, motor_vehicle_theft, simple_assault, intimidation, vandalism, weapons, drugs_alcohol, disorderly_conduct, trespass, theft_unspecified, assault_unspecified, other_offense, or a call_* type
limitNo
cursorNo
addressNoA U.S. street address
radius_mNoRadius in meters (default 500; plan caps apply)
record_typeNooffense, report, cfs (calls for service), unknown. Default leaves out cfs.
include_callsNoWhen true, calls for service and records that read as calls (alarms, traffic, welfare checks) are included. Default false, unless crime names a call type or record_type includes cfs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_calls / description
      Previous value: -"Include calls for service and records that read as calls (alarms, traffic, welfare checks). Default false, unless crime names a call type or record_type includes cfs."New value: +"When true, calls for service and records that read as calls (alarms, traffic, welfare checks) are included. Default false, unless crime names a call type or record_type includes cfs."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description carries real weight and does: it discloses redaction of sensitive cases, omission of sexual/domestic/juvenile records on free preview, plan caps on radius, and ignored parameters in preview mode. It stops short of describing pagination behavior for the cursor or rate/error behavior.

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?

Front-loaded with purpose and return fields, then plan/preview caveats. Dense and largely waste-free, though the closing preview sentence is a long run-on list that would read better as separate clauses.

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

Completeness3/5

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

Broad coverage for an 11-parameter tool with no output schema, but gaps remain: cursor semantics and paging (limit caps at 100) are never explained, nor is what 'source' or 'record type' values mean in results. Adequate but not fully complete for a tool of this complexity.

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 already 82%, yet the description adds meaning the schema does not: include_calls interacts with crime call types and record_type cfs, and radius/limit/from/to/filters/cursor are silently ignored on the free plan. That explains real parameter interactions rather than restating field definitions.

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?

Specific verb+resource: 'Police-published incident records around an address or point, newest first', followed by exactly which fields come back (what, when, block-level address, type, record type, source). An agent can distinguish this list-style lookup from aggregation siblings such as incident_stats or crime_index without opening a schema.

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?

Gives strong conditional guidance: calls are excluded unless include_calls is true, the full list requires Developer/Business plans, free plan returns a preview with a described subset, and cursor is refused there. No explicit routing to a sibling tool is given, which keeps it below a 5.

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.