Skip to main content
Glama

Fbi Crime

by io.github.pipeworx-io
OverviewAdmin

List Agencies

list_agencies
Read-onlyIdempotent

List reporting agencies (police departments / sheriffs) for a state. Returns ORI (Originating Reporting Identifier) — the canonical agency ID required by the other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
state_abbrYes2-letter state code (e.g., "CA"). Required: as of mid-2026 the all-agencies endpoint is gone and the API requires a state filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesRaw FBI CDE agencies response
stateYes2-letter state code if filtered, null if listing all agencies

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "state_abbr": "CA"
-  },
-  {}
-]New value: +[
+  {
+    "state_abbr": "CA"
+  }
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / state_abbr / description
      Previous value: -"2-letter state code (e.g., \"CA\"). Omit to list all."New value: +"2-letter state code (e.g., \"CA\"). Required: as of mid-2026 the all-agencies endpoint is gone and the API requires a state filter."
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "state_abbr"
+]
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "state_abbr": "CA"
+  },
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Raw FBI CDE agencies response",
+      "type": "object"
+    },
+    "state": {
+      "description": "2-letter state code if filtered, null if listing all agencies",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "state",
+    "data"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, etc., so the description's behavioral disclosure is consistent. It adds value by mentioning the API change in mid-2026 and that ORI is required by other tools, beyond what annotations provide.

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?

Two sentences, no filler, front-loaded with the main purpose and key detail about ORI. Every sentence earns its place.

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?

Given the tool's simplicity, comprehensive annotations, and presence of output schema, the description is fully sufficient. It explains the return value's importance and the required parameter's rationale.

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?

With 100% schema coverage and one parameter, the description reinforces the parameter's purpose and adds context about the API change that necessitates the parameter, going beyond the schema description.

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 'list reporting agencies (police departments / sheriffs) for a state' and highlights the return value (ORI) as the canonical ID needed by other tools, distinguishing it from siblings like 'get_agency'.

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?

The description specifies that the tool is for a single state and explains why the state parameter is required (the all-agencies endpoint is gone). It does not explicitly state when not to use or list alternatives, 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.

All Fbi Crime toolsInspect
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.

Resources