FBI NIBRS Crime Data

get_offense_estimates

Get NIBRS offense-level estimates (person or property crimes).

Returns offense-level data (as opposed to incident-level). An incident
may involve multiple offenses, so offense counts are typically higher
than incident counts.

Args:
    crime_category: 'person' for violent crimes or 'property' for
        property crimes. Default: 'person'.
    indicator: Filter by offense type.
    domain: Filter by analysis domain.
    limit: Maximum results to return (default 50, max 1000).

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

Input Schema

Name	Required	Default
`limit`	No
`domain`	No
`indicator`	No
`crime_category`	No	person

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses that offense counts are typically higher than incident counts and mentions the limit, but lacks details on auth, rate limits, or side effects. The description is adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a clear one-sentence purpose followed by parameter details. Every sentence adds value, and it is front-loaded with the core functionality.

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?

Given the tool has an output schema and four parameters, the description covers the key aspects: purpose, parameter meanings, and the offense vs. incident distinction. It lacks edge cases or examples but is complete enough for typical use.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates by explaining all four parameters: crime_category (with values 'person'/'property' and default), indicator, domain, and limit (with default and max). This adds essential meaning beyond the bare 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 clearly states the tool returns NIBRS offense-level estimates for person or property crimes, contrasting with incident-level data, which distinguishes it from sibling tools like get_property_incident_estimates.

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?

It explains that offense-level data differs from incident-level and provides defaults, but does not explicitly specify when to use this tool over alternatives, leaving some implicit guidance.

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

All FBI NIBRS Crime Data 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?