fbi-crime-mcp-server

FBI Search Agencies

fbi_search_agencies

Read-onlyIdempotent

Find law enforcement agencies in one state and their nine-character ORI codes, the identifier agency scope needs in fbi_get_crime_estimates, fbi_get_hate_crimes, fbi_get_arrests, and fbi_get_nibrs_breakdown. Fetches the state's full FBI CDE agency directory, filters it by words in the agency name, county, and agency type, sorts by agency name then ORI, and returns one page with the total match count and next_offset for the following page. Each agency carries its type, counties, and NIBRS reporting status. A code CDE has no directory for (AS, MP, or an unrecognized code) returns zero agencies with a notice.

Input Schema

Name	Required	Description
`limit`	No	Agencies per page (1–200). Defaults to 50.
`county`	No	County name, case-insensitive (e.g. Bexar). Matches an agency when it equals any of the agency's counties, so an agency serving several counties matches each of them.
`offset`	No	Zero-based position in the sorted matches; pass next_offset from the previous page. Defaults to 0.
`state_abbr`	Yes	Two ASCII-letter state abbreviation (e.g. TX, DC, PR); case-insensitive.
`agency_type`	No	Agency type: City, County, Other State Agency, Other, State Police, University or College, or Tribal.
`name_contains`	No	Words or word fragments that must all appear in the agency name, in any order, case-insensitively (e.g. "san antonio police").

Output Schema

Name	Required	Description
`cap`	No	The limit applied to this page.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Agencies on this page.
`total`	No	Agencies matching the filters across the whole state directory, before paging.
`notice`	No	Why the page is empty or partial, and the call to make next.
`offset`	No	Zero-based position of the first agency on this page.
`agencies`	No	This page of matching agencies, sorted by agency name, then ORI.
`truncated`	No	True when more matching agencies follow this page; continue from next_offset.
`state_abbr`	No	State code the directory was fetched for, uppercased.
`next_offset`	No	Offset of the next page; absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description provides significant behavioral context beyond the annotations. It details the pagination mechanism (total match count, next_offset), specific data fields returned for each agency (NIBRS status), and a precise edge case handling protocol for unrecognized CDE codes.

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 highly informative, which necessitates some density. However, it is well-structured by front-loading the core purpose and then detailing the mechanism and outcomes.

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?

For a complex directory service with multiple inputs and paginated results, the definition is extremely complete. It covers the function, the filtering, the data fields, and the termination condition (unrecognized code), leaving minimal ambiguity for the agent.

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?

Although schema coverage is 100%, the description adds critical semantic value by detailing the filtering scope (name, county, and type) and specifying the sorting order (agency name then ORI). This helps the agent refine complex input parameters.

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 identifies the resource ('law enforcement agencies') and the primary output ('nine-character ORI codes'). It also explicitly links the result to the dependent sibling tools (fbi_get_crime_estimates, etc.), providing strong context for selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Usage is highly guided because the description outlines its function as a necessary prerequisite for several other tools. By stating that it provides the specific 'ORIs' needed for other API calls, it defines the essential use case for the agent.

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

All fbi-crime-mcp-server 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.