FBI NIBRS Crime Data

get_victimization_data

Get NIBRS victimization counts and percentages.

Returns victim-level data from NIBRS including demographics of
victims, victim-offender relationships, and injury types. Useful
for understanding who is affected by crime and in what ways.

Args:
    indicator: Filter by offense type (e.g. 'Aggravated Assault',
        'NIBRS crimes against persons (Total)').
    domain: Filter by analysis domain (e.g. 'Victim-offender relationship',
        'Injury', 'Age', 'Sex', 'Race').
    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_victimization_data"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden. It indicates a read operation ('Get', 'Returns') but does not disclose potential safety concerns, data freshness, rate limits, or required authentication. The behavioral details are minimal but not misleading.

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: two sentences for purpose and a bullet-style list for arguments. It is front-loaded with the primary purpose and avoids unnecessary verbosity, making it easy for an agent to parse quickly.

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 a moderate complexity (3 optional parameters, no enums, an output schema), the description covers key aspects: what data is returned and how to filter. It does not explain output schema details (but that is handled by the output schema) or pagination beyond limit. Overall adequate for agent 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 schema has 0% coverage (no descriptions in schema), so the description must compensate. It clearly explains each parameter: 'indicator' filters by offense type, 'domain' by analysis domain, and 'limit' by maximum results with defaults and max. This adds essential meaning beyond the schema titles.

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 explicitly states it retrieves 'NIBRS victimization counts and percentages' and 'victim-level data from NIBRS including demographics, victim-offender relationships, and injury types.' This clearly distinguishes it from sibling tools like 'get_offense_estimates' and 'get_violent_incident_estimates' which focus on offense or 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 Guidelines3/5

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

The description provides a usage hint ('Useful for understanding who is affected by crime') but does not explicitly state when to use this tool over alternatives or when not to use it. There is no mention of prerequisites or exclusions compared to sibling tools.

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?