FBI Crime Data

get_national_crime_estimates

Get national FBI crime trend estimates over a range of years.

Returns annual national crime estimate data from the FBI Crime Data
Explorer for the specified crime category.

Args:
    crime_type: Type of crime to query. Options: violent-crime, property-crime,
        burglary, larceny, motor-vehicle-theft, homicide, robbery,
        aggravated-assault. Default: violent-crime.
    from_year: Start year for the data range (default 2015).
    to_year: End year for the data range (default 2023).

Input Schema

TableJSON Schema

Name	Required	Default
`to_year`	No
`from_year`	No
`crime_type`	No	violent-crime

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It clearly states the tool returns annual national crime estimates from the FBI CDE and documents defaults. It does not disclose potential limitations, error behavior, or rate limits, but for a read-only query tool this is acceptable.

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 well-structured with an Args section, but the first two sentences are somewhat redundant ('Get...' and 'Returns...'). It remains efficient and front-loaded with the core purpose.

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?

With an output schema present, the description does not need to detail return values. It covers tool scope, available crime types, and year defaults, making it complete for a simple query tool despite the lack of explicit usage alternatives.

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 provides only types and defaults (0% schema description coverage). The description compensates by listing valid crime_type options, explaining from_year and to_year as a range, and specifying defaults, significantly adding value beyond 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 opens with 'Get national FBI crime trend estimates over a range of years,' which clearly specifies the verb, resource, and scope. It distinguishes itself from sibling tools like get_state_crime_estimates by emphasizing 'national' data.

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 implicitly conveys usage context by stating it returns national-level FBI data, which contrasts with state-focused siblings. However, it does not explicitly state when to prefer this tool or mention alternatives, so the guidance is implied rather than explicit.

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

All FBI 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.3/5.0

Disambiguation5/5

Each tool serves a clearly distinct purpose: national trends, state estimates, state arrests, and multi-state comparison. The overlapping state crime estimate tools are differentiated by single-year multi-state vs multi-year single-state, making confusion unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (compare_state_crime, get_national_crime_estimates, get_state_arrests, get_state_crime_estimates). The use of 'get' for standard queries and 'compare' for the comparative function is predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of accessing FBI crime data. Each tool addresses a fundamental query pattern—national, state, arrests, and comparison—without unnecessary redundancy.

Completeness4/5

The tool surface covers the main data access patterns: national trends, state estimates, state arrests, and cross-state comparison. A minor gap is the lack of national-level arrest trends, but the existing tools are sufficient for most core workflows.

Resources

Need Help?