Skip to main content
Glama

Acled

by io.github.pipeworx-io

Search Events

search_events
Read-onlyIdempotent

Search ACLED political-violence and protest events. Filter by country (use "|" to OR, e.g., "Ukraine|Russia"), region, event_type, actor, ISO country code, or date range. Returns date, lat/lon, actors, event type, fatalities, and source notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isoNoISO 3166-1 numeric country code (alternative to country)
yearNoRestrict to a calendar year
actorNoMatch actor1 or actor2 (partial substring ok)
limitNoRecords to return (1-5000, default 100; ACLED max-per-call is 5000)
regionNoACLED region (e.g., "Western Africa")
countryNoCountry name(s), pipe-separated for OR
event_typeNoBattles | Protests | Riots | Explosions/Remote violence | Violence against civilians | Strategic developments
event_date_toNoYYYY-MM-DD inclusive
fatalities_minNoMinimum fatalities filter
sub_event_typeNoOptional ACLED sub-event type
event_date_fromNoYYYY-MM-DD inclusive

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of events returned
eventsYesArray of conflict events

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "Ukraine|Russia",
+    "event_date_from": "2024-01-01",
+    "event_date_to": "2024-12-31",
+    "event_type": "Battles",
+    "limit": 500
+  },
+  {
+    "actor": "Civil society",
+    "event_type": "Protests",
+    "fatalities_min": 0,
+    "limit": 100,
+    "region": "Western Africa",
+    "year": 2023
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of events returned",
+      "type": "number"
+    },
+    "events": {
+      "description": "Array of conflict events",
+      "items": {
+        "properties": {
+          "actor1": {
+            "description": "Primary actor involved",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "actor2": {
+            "description": "Secondary actor involved",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "admin1": {
+            "description": "Primary administrative division",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "admin2": {
+            "description": "Secondary administrative division",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country": {
+            "description": "Country where event occurred",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "data_id": {
+            "description": "ACLED data identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "event_date": {
+            "description": "Date of event (ISO format)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "event_id_cnty": {
+            "description": "Country-specific event ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "event_type": {
+            "description": "Type of event (e.g., Battles, Protests)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fatalities": {
+            "description": "Number of fatalities (0 if not specified)",
+            "type": "number"
+          },
+          "iso": {
+            "description": "ISO 3166-1 numeric country code",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Latitude coordinate",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "location": {
+            "description": "Specific location name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Longitude coordinate",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "notes": {
+            "description": "Additional event notes",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "region": {
+            "description": "ACLED geographic region",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source": {
+            "description": "Data source",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source_scale": {
+            "description": "Scale of source coverage",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sub_event_type": {
+            "description": "Sub-category of event type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Year of event",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "events"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds context about the data source and return fields, enhancing transparency 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, no wasted words, front-loaded with purpose. Efficiently conveys key information.

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?

Covers purpose, filters, and output fields adequately for a search tool with output schema. Lacks mention of pagination but limit parameter is described in schema.

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?

Despite 100% schema coverage, description provides additional clarity (e.g., pipe-separated OR for country, lists event type values) and a concise overview, adding value beyond schema descriptions.

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?

Clearly states verb 'Search', specific resource 'ACLED political-violence and protest events', and lists filtering options. Distinguishes from siblings by focusing on ACLED data.

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?

Implies usage context (searching ACLED events) but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusionary guidance.

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

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

TDQS

A3.7/5.0
Disambiguation3/5

Many tools have overlapping purposes, especially the Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) which all serve similar data retrieval needs. Additionally, entity_profile, compare_entities, and recent_changes overlap in providing company information. Polymarket tools also have overlapping analysis functions. This can cause confusion for agents.

Naming Consistency2/5

Tool names are inconsistent in style and convention. Some use underscores (ai_visibility_check, ask_pipeworx), others are single words (forget, recall), and many lack a clear verb_noun pattern (pipeworx_feedback, polymarket_edges). This mixture of naming conventions reduces predictability.

Tool Count3/5

With 32 tools, the count is on the higher side but appropriate given the broad scope covering multiple domains (Pipeworx data, Polymarket betting, ACLED events, npm scanning, memory, etc.). However, some areas have only one or two tools, which feels sparse, and the overall set could be trimmed or better organized.

Completeness3/5

The tool set covers many domains but has notable gaps. For ACLED, only search and count tools exist without any update/delete capabilities. For Pipeworx, the tools are heavily read-focused with no apparent write operations. The broad scope makes completeness hard to assess, but some obvious lifecycle operations are missing.

Resources