FBI NIBRS Crime Data

get_violent_incident_estimates

Get national estimates of violent crime incidents from NIBRS.

Returns weighted national estimates of crimes against persons (violent
crimes) including aggravated assault, homicide, kidnapping, robbery,
and sex offenses. Data includes breakdowns by weapon, location type,
victim-offender relationship, and time of day.

Args:
    indicator: Filter by offense type (e.g. 'Aggravated Assault',
        'Robbery', 'NIBRS crimes against persons (Total)').
        Omit for all offense types.
    domain: Filter by analysis domain. Options include:
        'Incident count', 'Weapon involved', 'Location type',
        'Victim-offender relationship', 'Time of day- Incident time',
        'Multiple victims', 'Multiple offenders', 'Clearance',
        'Injury', 'MSA', 'Population group'. Omit for all.
    limit: Maximum results to return (default 50, max 1000).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`domain`	No
`indicator`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that data is weighted national estimates with breakdowns by weapon, location, etc. However, it does not state whether the operation is read-only or mention rate limits or authorization requirements. The behavior is well-described overall.

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 structured with a clear summary and an Args section, making it easy to scan. It is slightly verbose but each sentence adds value. No redundant 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?

Given three optional parameters and an output schema (not shown), the description covers the return content (breakdowns) and parameter semantics adequately. It does not mention edge cases or error handling, but is sufficient 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?

The description compensates for the 0% schema coverage by thoroughly explaining each parameter: indicator with examples, domain with a list of options, and limit with default and maximum. This adds significant meaning beyond what the raw schema provides.

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 specifies the verb ('get') and resource ('national estimates of violent crime incidents from NIBRS'), and explicitly mentions it covers crimes against persons like aggravated assault, homicide, etc. This differentiates it from sibling tools like get_property_incident_estimates, which focus on property crimes.

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?

The description implies when to use the tool (when needing national violent crime estimates) but does not explicitly state when not to use it or provide direct comparisons with siblings. It provides clear domain and indicator options, which helps guide usage.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct level of crime data: offense estimates, property incidents, violent incidents, and victimization. No overlap in purpose.

Naming Consistency5/5

All tools follow a consistent 'get_' prefix with descriptive snake_case noun phrases, e.g., get_offense_estimates, get_violent_incident_estimates.

Tool Count5/5

With 4 tools, the server covers the main facets of NIBRS data without being too sparse or overwhelming.

Completeness5/5

The tool set covers offense-level, incident-level (property and violent), and victim-level data, providing a comprehensive surface for NIBRS crime queries.

Resources

Need Help?