Skip to main content
Glama
Sign In

Fbi Crime

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Agency Summary

agency_summary
Read-onlyIdempotent

Summarized monthly counts of an offense for one agency (by ORI). Returns time-series of victims/incidents/offenders.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ori": "CA0194200",
      "offense": "assault"
    },
    "name": "agency_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd month: MM-YYYY, YYYY-MM, or YYYY
oriYes9-character ORI
fromNoStart month: MM-YYYY, YYYY-MM, or YYYY
offenseYesOffense slug

Output Schema

NameRequiredDescriptionDefault
toYesEnd date in YYYY-MM format
oriYes9-character ORI identifier
dataYesRaw FBI CDE agency summary with victims/incidents/offenders time-series
fromYesStart date in YYYY-MM format
offenseYesOffense slug queried

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"YYYY-MM"New value: +"Start month: MM-YYYY, YYYY-MM, or YYYY"
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM"New value: +"End month: MM-YYYY, YYYY-MM, or YYYY"
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "offense": "assault",
+    "ori": "CA0194200"
+  },
+  {
+    "from": "2023-06",
+    "offense": "theft",
+    "ori": "TX0110200",
+    "to": "2024-06"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Raw FBI CDE agency summary with victims/incidents/offenders time-series",
+      "type": "object"
+    },
+    "from": {
+      "description": "Start date in YYYY-MM format",
+      "type": "string"
+    },
+    "offense": {
+      "description": "Offense slug queried",
+      "type": "string"
+    },
+    "ori": {
+      "description": "9-character ORI identifier",
+      "type": "string"
+    },
+    "to": {
+      "description": "End date in YYYY-MM format",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ori",
+    "offense",
+    "from",
+    "to",
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds that it returns a time-series of victims/incidents/offenders, which provides moderate added value beyond annotations.

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, front-loaded with purpose. Every word is necessary, no fluff. Highly efficient and structured.

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 existence of an output schema, the description adequately covers the tool's purpose and output. It could mention prerequisites or format, but overall sufficient for a read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions. The description does not add new semantic meaning to parameters beyond what the schema already provides, so baseline score applies.

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 provides summarized monthly counts of an offense for a single agency by ORI, and returns a time-series. This distinguishes it from sibling tools like state_summary (likely multi-agency) and list_agencies (no summary).

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 use for single-agency offense time-series but does not explicitly contrast with alternatives like state_summary or national_estimate. No when-not guidance is provided.

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
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.

Resources