FBI Crime Data

get_state_crime_estimates

Get FBI crime estimates for a US state over a range of years.

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

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY').
    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
`state`	Yes
`to_year`	No
`from_year`	No
`crime_type`	No	violent-crime

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description must disclose behavior. It mentions the data source (FBI Crime Data Explorer) and return type (annual crime estimate data), indicating a read-only operation. It lacks details on edge cases or data availability, but the provided context is solid for a query 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 concise, with a one-sentence summary and structured Args block. No wasted words; all information is relevant and easy to scan.

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 output schema exists, the description doesn't need return details. It covers all parameters, defaults, and data provenance. A minor gap is the absence of guidance on data coverage or limitations, but overall it is complete for a typical state crime query.

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 only provides types and defaults, while the description enumerates valid crime_type options, the state abbreviation format, and explains each parameter's meaning with defaults. This fully compensates for the schema's lack of descriptions.

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 FBI crime estimates for a US state over a range of years,' a specific verb+resource+scope. It clearly distinguishes from siblings like get_national_crime_estimates and get_state_arrests by focusing on state-level estimates.

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 explicitly states the tool retrieves state-specific data over a range of years, making the context clear. However, it does not mention alternatives or exclusions, so it doesn't fully guide selection among 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 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?