Ai Incident Db

Get Incident

get_incident

Read-onlyIdempotent

Fetch a full AI Incident Database record by numeric incident_id; returns title, date, description, alleged deployer/developer/harmed parties, and all linked news report URLs.

Input Schema

Name	Required	Description	Default
`incident_id`	Yes	Numeric AIID incident id

Output Schema

Name	Required	Description	Default
`incident`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 3, 2026

removedOutput schema / properties / AllegedDeployerOfAISystem

Removed value: -{
-  "description": "Organizations that deployed the AI system",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / AllegedDeveloperOfAISystem

Removed value: -{
-  "description": "Organizations that developed the AI system",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / AllegedHarmedOrNearlyHarmedParties

Removed value: -{
-  "description": "Parties harmed or nearly harmed",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / date

Removed value: -{
-  "description": "Incident date",
-  "type": "string"
-}

removedOutput schema / properties / description

Removed value: -{
-  "description": "Full incident description",
-  "type": "string"
-}

removedOutput schema / properties / editors

Removed value: -{
-  "description": "Editors who contributed to this incident record",
-  "items": {
-    "properties": {
-      "userId": {
-        "description": "Editor user identifier",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / editors_notes

Removed value: -{
-  "description": "Editorial notes",
-  "type": "string"
-}

addedOutput schema / properties / incident

Added value: +{
+  "properties": {
+    "AllegedDeployerOfAISystem": {
+      "items": {
+        "properties": {
+          "entity_id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "AllegedDeveloperOfAISystem": {
+      "items": {
+        "properties": {
+          "entity_id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "AllegedHarmedOrNearlyHarmedParties": {
+      "items": {
+        "properties": {
+          "entity_id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "date": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "editors": {
+      "items": {
+        "properties": {
+          "userId": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "incident_id": {
+      "type": "number"
+    },
+    "reports": {
+      "items": {
+        "properties": {
+          "authors": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "date_published": {
+            "type": "string"
+          },
+          "language": {
+            "type": "string"
+          },
+          "report_number": {
+            "type": "number"
+          },
+          "source_domain": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / incident_id

Removed value: -{
-  "description": "Unique incident identifier",
-  "type": "number"
-}

removedOutput schema / properties / reports

Removed value: -{
-  "description": "Linked news reports and sources",
-  "items": {
-    "properties": {
-      "authors": {
-        "description": "Report authors",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "date_published": {
-        "description": "Publication date",
-        "type": "string"
-      },
-      "language": {
-        "description": "Language code of the report",
-        "type": "string"
-      },
-      "report_number": {
-        "description": "Report identifier",
-        "type": "number"
-      },
-      "source_domain": {
-        "description": "Domain of the report source",
-        "type": "string"
-      },
-      "title": {
-        "description": "Report title",
-        "type": "string"
-      },
-      "url": {
-        "description": "URL to the report",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / title

Removed value: -{
-  "description": "Incident title",
-  "type": "string"
-}

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "incident_id": 42
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "AllegedDeployerOfAISystem": {
+      "description": "Organizations that deployed the AI system",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "AllegedDeveloperOfAISystem": {
+      "description": "Organizations that developed the AI system",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "AllegedHarmedOrNearlyHarmedParties": {
+      "description": "Parties harmed or nearly harmed",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "date": {
+      "description": "Incident date",
+      "type": "string"
+    },
+    "description": {
+      "description": "Full incident description",
+      "type": "string"
+    },
+    "editors": {
+      "description": "Editors who contributed to this incident record",
+      "items": {
+        "properties": {
+          "userId": {
+            "description": "Editor user identifier",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "editors_notes": {
+      "description": "Editorial notes",
+      "type": "string"
+    },
+    "incident_id": {
+      "description": "Unique incident identifier",
+      "type": "number"
+    },
+    "reports": {
+      "description": "Linked news reports and sources",
+      "items": {
+        "properties": {
+          "authors": {
+            "description": "Report authors",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "date_published": {
+            "description": "Publication date",
+            "type": "string"
+          },
+          "language": {
+            "description": "Language code of the report",
+            "type": "string"
+          },
+          "report_number": {
+            "description": "Report identifier",
+            "type": "number"
+          },
+          "source_domain": {
+            "description": "Domain of the report source",
+            "type": "string"
+          },
+          "title": {
+            "description": "Report title",
+            "type": "string"
+          },
+          "url": {
+            "description": "URL to the report",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Incident title",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description adds a return-content summary (title, date, parties, report URLs), but an output schema exists, so that information largely duplicates structured data. No mention of error behavior or missing-record handling.

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?

One front-loaded sentence: verb and resource first, then return contents. No filler or redundancy.

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 rich annotations, an output schema, and full schema coverage, the description only needs to establish purpose and it does. The minor gap is the absence of routing guidance relative to search_incidents, which an agent would benefit from.

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% and the single parameter is already documented as 'Numeric AIID incident id'. The description restates the same fact ('numeric incident_id') without adding format, range, or lookup guidance. Baseline 3 applies when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Fetch) and resource (AI Incident Database record) scoped to a numeric incident_id. The 'by numeric incident_id' framing implicitly separates it from the id-less sibling search_incidents, but it never names that sibling explicitly, so the differentiation is inferred rather than stated.

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 phrase 'by numeric incident_id' implies the precondition (you must already hold an ID, presumably obtained from search_incidents), but there is no explicit when-to-use, when-not, or named alternative. Usage is left to inference.

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

All Ai Incident Db tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.