FBI NIBRS Crime Data

get_property_incident_estimates

Get national estimates of property crime incidents from NIBRS.

Returns weighted national estimates of crimes against property
including burglary, larceny-theft, motor vehicle theft, arson,
and fraud. Data includes breakdowns by location type, time of day,
and clearance status.

Args:
    indicator: Filter by offense type (e.g. 'Burglary/Breaking & Entering',
        'Larceny/Theft Offenses', 'Motor Vehicle Theft',
        'NIBRS crimes against property (Total)').
    domain: Filter by analysis domain (e.g. 'Incident count',
        'Location type', 'Clearance', 'Time of day- Incident time').
    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

A3.7/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond what the tool returns (weighted estimates). It lacks information about required authentication, rate limits, data freshness, or side effects, which are not critical for a read-only tool but could be useful.

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 concise with a clear two-sentence introduction followed by a structured parameter list. It front-loads the tool's purpose and provides necessary details without unnecessary repetition.

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's simplicity (3 optional parameters, output schema exists), the description adequately covers the input parameters and general output. It could benefit from a brief note on typical use cases or data source, but it is mostly complete.

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?

The description provides detailed explanations for each parameter in the Args section, including examples for 'indicator' and 'domain' and constraints for 'limit' (default 50, max 1000). Since the schema has no parameter descriptions (0% coverage), this adds significant value.

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 it returns national estimates of property crime incidents from NIBRS, listing specific crime types (burglary, larceny-theft, etc.). The tool name and description distinguish it from siblings like get_violent_incident_estimates (violent crimes) and get_offense_estimates (general offenses).

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 implies usage for property crime estimates but does not explicitly state when to use this tool versus siblings or when not to use it. No alternative tools or exclusions are mentioned.

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?