Skip to main content
Glama

fbi-crime-mcp-server

FBI Get NIBRS Breakdown

fbi_get_nibrs_breakdown
Read-onlyIdempotent

NIBRS incident breakdowns reported to FBI CDE for one offense, for the nation, a state, or an agency, summed over a month window from January 1991 through the current year. Returns victim counts by age, sex, race, location, ethnicity, and relationship to the offender; offender counts by age, sex, race, and ethnicity; and offense counts by weapon and related offense, with every category CDE reports, zeros included. Each dimension is tallied separately and their sums can differ, so no dimension stands in for another's total. offense is required (codes are listed on the field). National scope omits identifiers; state requires only state_abbr; agency requires only ori (look it up with fbi_search_agencies). When CDE has no value for any category, as for an unrecognized state or ORI, a window with no NIBRS data, or an offense with no reported incidents in the window, the call fails with no_data.

Input Schema

NameRequiredDescriptionDefault
oriNoNine ASCII-letter/digit ORI code (e.g. CA0010400, DCMPD0000); case-insensitive. Find an agency's ORI with fbi_search_agencies. Only permitted and required for agency scope.
scopeYesGeographic scope: national (omit identifiers), state (only state_abbr), or agency (only ori).
offenseYesNIBRS offense code to break down (required; case-insensitive). Codes: 100 Kidnapping/Abduction; 101 Treason; 103 Espionage; 120 Robbery; 200 Arson; 210 Extortion/Blackmail; 220 Burglary/Breaking & Entering; 240 Motor Vehicle Theft; 250 Counterfeiting/Forgery; 270 Embezzlement; 280 Stolen Property Offenses; 290 Destruction/Damage/Vandalism of Property; 360 Failure to Register as a Sex Offender; 370 Pornography/Obscene Material; 510 Bribery; 520 Weapon Law Violations; 521 Violation of National Firearm Act of 1934; 522 Weapons of Mass Destruction; 526 Explosives Violation; 620 Wildlife Trafficking; 720 Animal Cruelty; 09A Murder and Nonnegligent Manslaughter; 09B Negligent Manslaughter; 09C Justifiable Homicide; 11A Rape; 11B Sodomy; 11C Sexual Assault With An Object; 11D Criminal Sexual Contact; 13A Aggravated Assault; 13B Simple Assault; 13C Intimidation; 23A Pocket-picking; 23B Purse-snatching; 23C Shoplifting; 23D Theft From Building; 23E Theft From Coin-Operated Machine or Device; 23F Theft From Motor Vehicle; 23G Theft of Motor Vehicle Parts or Accessories; 23H All Other Larceny; 26A False Pretenses/Swindle/Confidence Game; 26B Credit Card/Automated Teller Machine Fraud; 26C Impersonation; 26D Welfare Fraud; 26E Wire Fraud; 26F Identity Theft; 26G Hacking/Computer Invasion; 26H Money Laundering; 30A Illegal Entry into the United States; 30B False Citizenship; 30C Smuggling Aliens; 30D Re-entry after Deportation; 35A Drug/Narcotic Violations; 35B Drug Equipment Violations; 36A Incest; 36B Statutory Rape; 39A Betting/Wagering; 39B Operating/Promoting/Assisting Gambling; 39C Gambling Equipment Violation; 39D Sports Tampering; 40A Prostitution; 40B Assisting or Promoting Prostitution; 40C Purchasing Prostitution; 49A Harboring Escapee/Concealing from Arrest; 49B Flight to Avoid Prosecution; 49C Flight to Avoid Deportation; 58A Import Violations; 58B Export Violations; 61A Federal Liquor Offenses; 61B Federal Tobacco Offenses; 64A Human Trafficking, Commercial Sex Acts; 64B Human Trafficking, Involuntary Servitude.
to_yearYesEnd year of the data range (inclusive), 1991 through the current year.
to_monthNoEnd month (1–12). Defaults to December.
from_yearYesStart year of the data range (inclusive), 1991 through the current year. The API uses monthly granularity.
from_monthNoStart month (1–12). Defaults to January.
state_abbrNoTwo ASCII-letter state abbreviation (e.g. CA, DC, PR); case-insensitive. Only permitted and required for state scope.

Output Schema

NameRequiredDescriptionDefault
toNoLast month of the summed window (MM-YYYY).
oriNoUppercased ORI code; present only for agency scope.
fromNoFirst month of the summed window (MM-YYYY).
errorNoPresent when the call failed. Absent on success.
scopeNoGeographic scope queried.
victimNoVictim counts summed over the window.
offenseNoNIBRS offense code applied.
offenderNoOffender counts summed over the window.
state_abbrNoUppercased state abbreviation; present only for state scope.
max_data_dateNoLatest data month CDE reports (MM/YYYY); absent when CDE omits it.
offense_labelNoCDE label for the applied offense code.
offense_detailsNoCDE's offense section (weapons and related offenses) summed over the window.
data_last_updatedNoDate CDE last refreshed NIBRS data; absent when CDE omits it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent/open-world annotations, it discloses the returned breakdown dimensions, zero-inclusion behavior, independent tallies per dimension, and concrete no_data failure cases. This is substantial behavioral context for an agent invoking the tool.

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 dense but front-loaded with purpose, return shape, scope rules, and failure behavior. Every clause carries operational value for this relatively complex query tool.

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

Completeness5/5

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

It covers scope selection, required offense, temporal range, returned breakdown dimensions, and expected failure behavior. With the output schema and annotations also present, an agent has enough context to invoke this tool 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?

Schema description coverage is 100%, so the schema already documents the parameters thoroughly. The description reinforces required offense, scope-specific identifier rules, and ORI lookup, but mostly repeats information available 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 names a specific operation and resource: NIBRS incident breakdowns for one offense across national, state, or agency scope. It clearly distinguishes the tool from broad crime, arrest, hate crime, and LEOKA siblings by focusing on NIBRS incident breakdown dimensions.

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 gives clear usage conditions for each scope and explicitly directs agency lookup to fbi_search_agencies, plus failure conditions for no_data. It does not explicitly compare when to use this versus each sibling analysis tool, but the context is clear.

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.