offnadir-delta-mcp 1.28.0 → 1.29.0

package/README.md

@@ -16,7 +16,7 @@ satellite can actually resolve it, and produce a collection-ready plan.
 Real-time event and geospatial intelligence for OSINT, geopolitical risk, and GEOINT work —
 source-linked, geolocated, and current, not a training snapshot.
 
-`41` tools · MCP server version `1.28.0` · [full reference](https://offnadir-delta.com/docs/mcp)
+`42` tools · MCP server version `1.29.0` · [full reference](https://offnadir-delta.com/docs/mcp)
 
 ## What it does
 
@@ -77,7 +77,7 @@ locally from a generated catalog, so registries can introspect it without creden
 
 ### First call — free
 
-23 of the 41 tools cost nothing, so the first thing you run is free:
+23 of the 42 tools cost nothing, so the first thing you run is free:
 
 > Give me the latest Daily World Brief. Lead with the three most significant developments,
 > explain why each matters, and cite the supporting signals.
@@ -95,15 +95,15 @@ What is happening, where it concentrates, and what today looks like.
 
 | Tool | What it does | Cost |
 | --- | --- | --- |
-| `query_signals` | Query geolocated world event signals (Delta Signals: geopolitical, security, disaster, and infrastructure events distilled from global news media, AI-enriched with severity/GEOINT scores and satellite-collection recommendations). | 3 tok |
-| `query_stats` | Aggregate statistics over the signal corpus — total event count plus per-category and per-day breakdown (trend) for a bounding box and date window. | 1 tok |
-| `query_hotspots` | Geographic hotspots — signal density grid-binned into cells, ranked by event count, each with peak severity, the categories present, and up to 5 representative event_ids (trace a cell back to its signals). | 1 tok |
-| `get_world_brief` | Fetch the Daily World Brief — an AI-synthesized OSINT/GEOINT digest of the previous UTC day's worldwide event signals (headline, executive summary, top developments with why-it-matters and what-to-watch, per-theme roll-up, ranked signals). | free |
-| `query_developments` | What actually CHANGED about the events in an area — not which articles are new. | 3 tok |
-| `get_event_thread` | The full history of ONE event: its current state, and every change in the order it happened. | free |
-| `search_entities` | Find a place in the location registry — ports and harbours, military bases and airfields, power and energy plants, maritime chokepoints and named seas. | 1 tok |
-| `get_entity` | What has happened at one place. | 1 tok |
-| `get_related_events` | What else connects to one event, and what came before and after it. | 3–8 tok |
+| `query_signals` | Geolocated world events (geopolitical, security, disaster, infrastructure) from global news media, AI-enriched with severity/GEOINT scores and collection recommendations. | 3 tok |
+| `query_stats` | Roll-ups over the corpus: totals plus per-category and per-day breakdown. | 1 tok |
+| `query_hotspots` | Where activity concentrates: density grid-binned into ranked cells with peak severity, categories and representative event_ids. | 1 tok |
+| `get_world_brief` | The Daily World Brief — an AI digest of the previous UTC day. | free |
+| `query_developments` | What actually CHANGED about the events in an area, not which articles are new. | 3 tok |
+| `get_event_thread` | One event end to end: state plus every change in order — the "new event or update" distinction a feed cannot make. | free |
+| `search_entities` | Find a place in the location registry — ports, bases, airfields, power plants, chokepoints, named seas. | 1 tok |
+| `get_entity` | What has happened at one place: the registry record plus every linked event with HOW it was linked. | 1 tok |
+| `get_related_events` | What else connects to one event, and what came before and after. | 3–8 tok |
 
 ### Plan
 
@@ -111,14 +111,14 @@ Whether a satellite can resolve it, which one, and when it next passes.
 
 | Tool | What it does | Cost |
 | --- | --- | --- |
-| `search_imagery` | Search the satellite imagery catalog (Sentinel-1, Sentinel-2, NISAR L-band) for scenes over an area and date window — the natural follow-up to a signal (find imagery over the event location). | 2 tok |
-| `plan_event_imagery` | Plan the imagery evidence for ONE event in a single call, instead of guessing collections one at a time. | 4 tok |
-| `rank_imaging_priority` | WHERE — and with what class (and therefore cost) of satellite — is observation most worthwhile right now? | 1 tok |
-| `survey_observable_events` | Which events in a window can a given in-app sensor actually RESOLVE? | 1 tok |
-| `predict_satellite_passes` | WHEN can this place next be imaged, and by WHAT — the timing half of collection planning. | 2 tok |
-| `test_hypotheses` | Given competing statements, return the observation that would REFUTE the most of them — and, in the same answer, the observations that would refute none of them however convincing they look. | 3 tok |
-| `lookup_elevation` | Measure terrain height from the Copernicus DEM GLO-30 — a point (lat + lon), an area (bbox), or a drawn polygon, for which the statistics are computed over the samples INSIDE the ring rather than its bounding box. | free |
-| `analyze_terrain` | Compute FROM the terrain rather than reading heights out of it (that is lookup_elevation). | free |
+| `search_imagery` | Search the imagery catalog (Sentinel-1, Sentinel-2, NISAR L-band) over an area and window. | 2 tok |
+| `plan_event_imagery` | The deterministic imagery plan for ONE event: checks BOTH sensors exactly once — sentinel-1-grd (SAR, the only look that survives cloud and night) and sentinel-2-l2a — against the event footprint and a pre/post window. | 4 tok |
+| `rank_imaging_priority` | WHERE, and with what class of satellite, observation is most worthwhile now: composite IMPORTANCE crossed with the SPEC CLASS the required resolution demands — coarse, hr (free Sentinel-class) or vhr. | 1 tok |
+| `survey_observable_events` | Which events a sensor can actually RESOLVE, over the FULL set. | 1 tok |
+| `predict_satellite_passes` | WHEN a place can next be imaged and by WHAT: SGP4 over day-cached elements for 13 free-systematic and commercial-taskable families. | 2 tok |
+| `test_hypotheses` | Given competing statements, the observation that would REFUTE the most — and those that would refute none. | 3 tok |
+| `lookup_elevation` | Terrain height from the Copernicus DEM GLO-30 for a point, bbox or polygon, with relief — the number that governs SAR layover and shadow. | free |
+| `analyze_terrain` | Compute FROM the terrain. | free |
 
 ### Analyze
 
@@ -126,13 +126,13 @@ Turn reporting into a cited assessment you can audit afterwards.
 
 | Tool | What it does | Cost |
 | --- | --- | --- |
-| `assess_signal` | Run an AI RS (remote-sensing) deep-dive assessment for a specific signal: what to observe, recommended sensors, and a collection window. | 5/15 tok |
-| `ask_analyst` | Ask the Delta Analyst an OSINT/GEOINT question. | 5–123 tok |
-| `get_analyst_job` | Fetch the status and result of an ask_analyst run by job_id. | free |
-| `query_claims` | Read the LEDGER of claims this key has been given — every factual assertion the Analyst made, with its evidence class (CONFIRMED / REPORTED / PARTY_CLAIM / ASSESSMENT), how many INDEPENDENT source families backed it, and the publishers. | free |
-| `refine_location` | Research one signal's location further and, if the sources genuinely narrow it, store and return the better coordinate. | 3–29 tok |
-| `measure_index_series` | Measure a spectral index over an area, scene by scene, back through the Sentinel-2 archive — the answer to "how has this changed since <year>". | 0.5 tok |
-| `detect_ships` | Count vessel-like targets in ONE SAR scene over an area, using CFAR detection on Sentinel-1. | 5 tok |
+| `assess_signal` | AI remote-sensing deep-dive for one signal: what to observe, sensors, a collection window. | 5/15 tok |
+| `ask_analyst` | Ask the Delta Analyst an OSINT/GEOINT question; returns a structured brief. | 5–123 tok |
+| `get_analyst_job` | Status and result of an ask_analyst run. | free |
+| `query_claims` | The ledger of claims this key was given, each with its evidence class, independent source families and publishers. | free |
+| `refine_location` | Research one signal's location further and store a better coordinate if the sources genuinely narrow it. | 3–29 tok |
+| `measure_index_series` | Measure a spectral index over an area scene by scene through the Sentinel-2 archive. | 0.5 tok |
+| `detect_ships` | Count vessel-like targets in ONE Sentinel-1 SAR scene by CFAR detection — radar sees through cloud and at night. | 5 tok |
 
 ### Watch
 
@@ -140,18 +140,19 @@ Stand up continuous coverage and be told only when the answer changes. Creating
 
 | Tool | What it does | Cost |
 | --- | --- | --- |
-| `create_standing_order` | Put an area under CONTINUOUS watch: save a question plus a bounding box and Delta re-answers it on a schedule, notifying only when the answer actually changed. | free |
-| `list_standing_orders` | List the standing orders on this key, with each one’s cadence, watched area, when it last checked, when it last actually fired, and how many consecutive checks found nothing (quiet_checks — a high number means the watch is not earning its place). | free |
-| `delete_standing_order` | Delete a standing order by id, or pause/resume it instead by passing active=false/true. | free |
-| `list_monitored_areas` | List the places under continuous satellite measurement on this key (Delta Watchlist measurements), with each area’s metric, most recent value, change since the previous measurement, whether that value was flagged anomalous, and coverage — how many acquisitions were measured versus how many exist. | free |
-| `get_monitored_area` | Fetch one monitored area with its full measurement history — every acquisition that was measured, its value, and whether it was flagged anomalous. | free |
-| `create_monitored_area` | Put a place under continuous satellite measurement: pick an area and what to count, and every new Sentinel-1 / Sentinel-2 / VIIRS acquisition over it is measured automatically from then on. | free |
-| `list_watches` | The Watchlist: everything this account keeps watch on — areas under satellite measurement, areas under event watch (standing orders), and real-world events being tracked — aggregated as one list with a state bucket per watch: needs_attention (anomaly, error, or a notable development), changed_today (a meaningful change in the last 24 h), awaiting_data, or stable. | free |
-| `get_watch` | One watch end to end, in a single call: its target, current state, latest meaningful change, measurements with their recent series, standing-order questions, and — for an event watch — the event’s verification state, casualty/attribution fields, recent developments, imagery availability, and the full event thread (timeline + sources). | free |
+| `create_standing_order` | Put an area under CONTINUOUS watch: a question plus a bbox, re-answered on a schedule, notifying only when the answer changed. | free |
+| `list_standing_orders` | The standing orders on this key: cadence, area, last check, last actual fire, and quiet_checks — a high quiet_checks means the watch is not earning its place. | free |
+| `delete_standing_order` | Delete a standing order, or pause/resume with active=false/true. | free |
+| `list_monitored_areas` | Places under continuous satellite measurement: metric, latest value, change, anomaly flag, coverage. | free |
+| `get_monitored_area` | One monitored area with its full measurement history. | free |
+| `create_monitored_area` | Put a place under continuous satellite measurement — every new Sentinel-1/2 or VIIRS acquisition is measured. | free |
+| `list_watches` | The Watchlist as one list, each entry with a state bucket. | free |
+| `get_watch` | One watch end to end: target, state, latest change, measurements with recent series, standing-order questions, and for an event watch its verification state, developments and thread, plus this account's notes. | free |
+| `get_decision_package` | Everything needed to decide what to collect next about one watch, in one object. | 5 tok |
 | `create_watch` | Add a target to the Watchlist. | free |
-| `update_watch` | Rename a watch, or pause and resume it. | free |
-| `delete_watch` | Delete a watch by id. | free |
-| `add_note` | Add a note to a watch, start a thread on it, or reply to one — one append-only ledger. | free |
+| `update_watch` | Rename, pause or resume a watch. | free |
+| `delete_watch` | Delete a watch and its underlying resources — bound monitored areas with their history, and standing orders. | free |
+| `add_note` | Add a note to a watch, start a thread, or reply. | free |
 | `delete_note` | Delete one note from a watch. | free |
 
 ### Workspace
@@ -160,9 +161,9 @@ The map assets you own — saved layer sets and your own uploaded data.
 
 | Tool | What it does | Cost |
 | --- | --- | --- |
-| `list_layer_sets` | List the layer sets saved on this account — the named map configurations a user builds in the app, each with how many layers it holds, its tags, when it was last changed and when it was last opened. | free |
-| `get_layer_set` | Read one saved layer set by id: its name, description, layer count, size, tags and timestamps. | free |
-| `list_uploaded_layers` | List the data this account uploaded to the map — name, format, size and when it was added — plus the formats the uploader actually accepts. | free |
+| `list_layer_sets` | The layer sets saved on this account. | free |
+| `get_layer_set` | One saved layer set by id. | free |
+| `list_uploaded_layers` | The data this account uploaded to the map, plus the formats the uploader accepts. | free |
 
 ### Account
 
@@ -170,7 +171,7 @@ Pre-flight your token balance before a metered call.
 
 | Tool | What it does | Cost |
 | --- | --- | --- |
-| `get_usage` | Check the calling key's remaining token balance and plan capabilities — monthly allocation, tokens used this period, tokens remaining, and whether the plan includes AI tools over the API (assess_signal / ask_analyst). | free |
+| `get_usage` | The calling key's remaining token balance and plan capabilities. | free |
 
 ## Pricing and metering