Skip to main content
Glama

Fbi Crime

by io.github.pipeworx-io
OverviewAdmin

State Summary

state_summary
Read-onlyIdempotent

Summarized monthly counts of an offense in a state. Returns time-series and totals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd month: MM-YYYY, YYYY-MM, or YYYY (default current)
fromNoStart month: MM-YYYY, YYYY-MM, or YYYY (default 5 years ago)
offenseYesOffense slug
state_abbrYes2-letter state code

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesEnd date in YYYY-MM format
dataYesRaw FBI CDE state summary time-series and totals
fromYesStart date in YYYY-MM format
stateYes2-letter state code
offenseYesOffense slug queried

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"YYYY-MM (default 5 years ago)"New value: +"Start month: MM-YYYY, YYYY-MM, or YYYY (default 5 years ago)"
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM (default current)"New value: +"End month: MM-YYYY, YYYY-MM, or YYYY (default current)"
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "offense": "burglary",
+    "state_abbr": "NY"
+  },
+  {
+    "from": "2022-01",
+    "offense": "robbery",
+    "state_abbr": "TX",
+    "to": "2024-12"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Raw FBI CDE state summary time-series and totals",
+      "type": "object"
+    },
+    "from": {
+      "description": "Start date in YYYY-MM format",
+      "type": "string"
+    },
+    "offense": {
+      "description": "Offense slug queried",
+      "type": "string"
+    },
+    "state": {
+      "description": "2-letter state code",
+      "type": "string"
+    },
+    "to": {
+      "description": "End date in YYYY-MM format",
+      "type": "string"
+    }
+  },
+  "required": [
+    "state",
+    "offense",
+    "from",
+    "to",
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which the description does not contradict. The description adds no extra behavioral context beyond the output (time-series and totals), so minimal value added.

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?

Single, clear sentence that front-loads the core purpose. No unnecessary words; every phrase earns its place.

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 a full schema and output schema present, the description adequately covers the tool's behavior. It could add more detail about the returned time-series format, but is still complete enough for an agent to use.

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 description coverage is 100%, so parameters are well-documented. The description does not add any meaning beyond what the schema provides, which is the baseline score for high coverage.

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?

Description clearly states the tool provides summarized monthly counts of an offense in a state, returning time-series and totals. It uses a specific verb+resource and distinguishes itself from siblings like agency_summary and national_estimate.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no exclusions or context for usage. The description omits any when-to-use or when-not-to-use information.

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