Skip to main content
Glama
Vortx-AI

emem

by Vortx-AI
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
Rust
Remote

Intent-routed planner

emem_intent

Resolve queries against shared memory by stating an intent type and required fields in one object; the answer returns in the same call. Supports location, similarity, change, and free-text queries.

Instructions

State what you want in one typed object and get the answer. You do not choose a primitive. type selects the intent AND the other fields that the tool reads. Send only the fields in its row. The plan runs in the same call: you get results, not a list of calls.

type | needs | optional | answers where_is | description | | cell64 for a named place what_is_here | cell OR place | description | what is attested at a location is_like | a, b | | cosine similarity of two cells did_change | cell, band, window | | delta for one band over [start,end] tslots find_like | key | k, filter | nearest cells by embedding confirm | claim, cell | | verdict and the signed facts behind it ask | description | place/cell/lat+lng | free-text question, packaged answer area_over_time | geometry, bbox OR areas; start_date, end_date | index, max_scenes | index of an area for each overpass, with spread and anomaly

An unknown or missing type returns a needs_intent_type envelope with the valid values. It is not a hard error.

When to use: Call this when the question matches one of the eight rows and you prefer to state the goal. Otherwise call the primitive. A band at a cell is emem_recall. A region is emem_recall_polygon. A free-text question about a place is emem_ask (type:"ask" sends it there). window takes tslots, not dates: get them from emem_trajectory. areas puts up to 6 areas on one chart. You can call a tool that this text names but your list does not show, by name, through tools/call.

Example arguments: {"type":"did_change","cell":"defi.zb64a.cAzU.zfa27","band":"indices.ndvi","window":[20245,20620]}

Input Schema

NameRequiredDescriptionDefault
aNois_like only: cell64 of the first place in the pair.
bNois_like only: cell64 of the second place. The answer is a cosine similarity in [-1,1] over the two cells' embeddings.
kNofind_like only: how many neighbours to return.
keyNofind_like only: cell64 to search from, ranked by embedding cosine.
latNoask only: latitude, paired with `lng`, when you want to pin the location by coordinate rather than by name or cell64.
lngNoask only: longitude, paired with `lat`.
bandNodid_change only: which band to test, e.g. "indices.ndvi". One band per call; the answer is a delta over `window`, not a whole-cell diff.
bboxNo
cellNocell64 address, e.g. "defi.zb64a.cAzU.zfa27". Required by did_change and confirm. Optional for what_is_here and ask: supply it to skip geocoding, omit it and give `place` instead.
typeYesWhich intent; the table in the description gives each row's fields.
areasNoarea_over_time: up to 6 {id,geometry|bbox} on one chart
claimNoconfirm only: the claim to test at `cell`, e.g. {"band":"indices.ndvi","op":"gt","value":0.4}. The answer is a verdict plus the signed facts it rests on.
indexNo
placeNoFree-text place name for what_is_here and ask when you have a name but no cell64, e.g. "Ashok Nagar, Ranchi". The responder geocodes it. Ignored when `cell` is present.
filterNofind_like only: optional claim constraining which cells may be returned. Same object as `claim` below, same ops, same required fields.
windowNodid_change only: exactly two tslots, [start, end], band-tempo-relative integers from the emem epoch (NOT unix seconds or a date string). Get valid tslots for a cell from emem_trajectory.
end_dateNoYYYY-MM-DD
geometryNoarea_over_time: GeoJSON Polygon; or bbox {min_lat,min_lng,max_lat,max_lng}.
max_scenesNo
start_dateNoYYYY-MM-DD
descriptionNowhere_is: the place to resolve, e.g. "Mount Everest". ask: the user's question, forwarded verbatim. what_is_here: optional free text used as the question and, if `place` is absent, as the place. Ignored by the other intents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.4.4
    • changedInput schema / description
      Previous value: -"A tagged union: `type` selects the intent and decides which OTHER fields are read. Fields belonging to a different intent are ignored, so send only the ones its row needs."New value: +"A tagged union on `type`; fields of other intents are ignored."
    • addedInput schema / properties / areas
      Added value: +{
+  "description": "area_over_time: up to 6 {id,geometry|bbox} on one chart",
+  "maxItems": 6,
+  "type": "array"
+}
    • addedInput schema / properties / bbox
      Added value: +{
+  "type": "object"
+}
    • changedInput schema / properties / cell / description
      Previous value: -"cell64 address, e.g. \"damO.zb000.xUti.zde78\". Required by did_change and confirm. Optional for what_is_here and ask: supply it to skip geocoding, omit it and give `place` instead."New value: +"cell64 address, e.g. \"defi.zb64a.cAzU.zfa27\". Required by did_change and confirm. Optional for what_is_here and ask: supply it to skip geocoding, omit it and give `place` instead."
    • addedInput schema / properties / claim / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean",
+  "array",
+  "null"
+]
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "YYYY-MM-DD",
+  "type": "string"
+}
    • addedInput schema / properties / filter / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean",
+  "array",
+  "null"
+]
    • addedInput schema / properties / geometry
      Added value: +{
+  "description": "area_over_time: GeoJSON Polygon; or bbox {min_lat,min_lng,max_lat,max_lng}.",
+  "type": "object"
+}
    • addedInput schema / properties / index
      Added value: +{
+  "enum": [
+    "ndvi",
+    "ndwi",
+    "ndmi",
+    "lswi",
+    "evi",
+    "vv",
+    "vh",
+    "vh_vv"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / k / description
      Previous value: -"find_like only: how many neighbours to return. Defaults to the primitive's own default when omitted."New value: +"find_like only: how many neighbours to return."
    • changedInput schema / properties / key / description
      Previous value: -"find_like only: cell64 to search from. Neighbours are ranked by embedding cosine against this cell."New value: +"find_like only: cell64 to search from, ranked by embedding cosine."
    • addedInput schema / properties / max_scenes
      Added value: +{
+  "maximum": 24,
+  "minimum": 3,
+  "type": "integer"
+}
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "YYYY-MM-DD",
+  "type": "string"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Which question you are asking, and therefore which other fields apply. where_is: name a place, get its cell64 (needs `description`). what_is_here: summarise a location (needs `cell`, OR `place`/`description` to resolve it first). is_like: pairwise similarity (needs `a` and `b`). did_change: did one band move over a time window (needs `cell`, `band`, `window`). find_like: nearest neighbours to a known cell (needs `key`; optional `k`, `filter`). confirm: is a claim true at a cell (needs `claim` and `cell`). ask: free-text question about a place, runs locate + topic-route + recall server-side (needs `description`; optional `place`/`cell`/`lat`+`lng` to pin the location)."New value: +"Which intent; the table in the description gives each row's fields."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "where_is",
-  "what_is_here",
-  "is_like",
-  "did_change",
-  "find_like",
-  "confirm",
-  "ask"
-]New value: +[
+  "where_is",
+  "what_is_here",
+  "is_like",
+  "did_change",
+  "find_like",
+  "confirm",
+  "ask",
+  "area_over_time"
+]
  2. Addedv1.3.9
  3. Removedv1.3.8
  4. Changed18 schema fields changedv1.3.3
    • addedInput schema / description
      Added value: +"A tagged union: `type` selects the intent and decides which OTHER fields are read. Fields belonging to a different intent are ignored, so send only the ones its row needs."
    • addedInput schema / properties / a / description
      Added value: +"is_like only: cell64 of the first place in the pair."
    • addedInput schema / properties / b / description
      Added value: +"is_like only: cell64 of the second place. The answer is a cosine similarity in [-1,1] over the two cells' embeddings."
    • addedInput schema / properties / band / description
      Added value: +"did_change only: which band to test, e.g. \"indices.ndvi\". One band per call; the answer is a delta over `window`, not a whole-cell diff."
    • addedInput schema / properties / cell / description
      Added value: +"cell64 address, e.g. \"damO.zb000.xUti.zde78\". Required by did_change and confirm. Optional for what_is_here and ask: supply it to skip geocoding, omit it and give `place` instead."
    • addedInput schema / properties / claim / description
      Added value: +"confirm only: the claim to test at `cell`, e.g. {\"band\":\"indices.ndvi\",\"op\":\"gt\",\"value\":0.4}. The answer is a verdict plus the signed facts it rests on."
    • addedInput schema / properties / description / description
      Added value: +"where_is: the place to resolve, e.g. \"Mount Everest\". ask: the user's question, forwarded verbatim. what_is_here: optional free text used as the question and, if `place` is absent, as the place. Ignored by the other intents."
    • addedInput schema / properties / filter
      Added value: +{
+  "description": "find_like only: optional claim constraining which cells may be returned, same shape as `claim`.",
+  "type": "object"
+}
    • addedInput schema / properties / k / description
      Added value: +"find_like only: how many neighbours to return. Defaults to the primitive's own default when omitted."
    • addedInput schema / properties / k / minimum
      Added value: +1
    • addedInput schema / properties / key / description
      Added value: +"find_like only: cell64 to search from. Neighbours are ranked by embedding cosine against this cell."
    • addedInput schema / properties / lat
      Added value: +{
+  "description": "ask only: latitude, paired with `lng`, when you want to pin the location by coordinate rather than by name or cell64.",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}
    • addedInput schema / properties / lng
      Added value: +{
+  "description": "ask only: longitude, paired with `lat`.",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}
    • addedInput schema / properties / place
      Added value: +{
+  "description": "Free-text place name for what_is_here and ask when you have a name but no cell64, e.g. \"Ashok Nagar, Ranchi\". The responder geocodes it. Ignored when `cell` is present.",
+  "type": "string"
+}
    • addedInput schema / properties / type / description
      Added value: +"Which question you are asking, and therefore which other fields apply. where_is: name a place, get its cell64 (needs `description`). what_is_here: summarise a location (needs `cell`, OR `place`/`description` to resolve it first). is_like: pairwise similarity (needs `a` and `b`). did_change: did one band move over a time window (needs `cell`, `band`, `window`). find_like: nearest neighbours to a known cell (needs `key`; optional `k`, `filter`). confirm: is a claim true at a cell (needs `claim` and `cell`). ask: free-text question about a place, runs locate + topic-route + recall server-side (needs `description`; optional `place`/`cell`/`lat`+`lng` to pin the location)."
    • addedInput schema / properties / window / description
      Added value: +"did_change only: exactly two tslots, [start, end], band-tempo-relative integers from the emem epoch (NOT unix seconds or a date string). Get valid tslots for a cell from emem_trajectory."
    • addedInput schema / properties / window / maxItems
      Added value: +2
    • addedInput schema / properties / window / minItems
      Added value: +2
  5. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses several behavioral traits: an unknown/missing type returns a needs_intent_type envelope rather than a hard error, the plan executes in the same call (results, not a call list), `window` is tslots not dates and must be sourced from emem_trajectory, and `areas` caps at 6. It does not address the tension that annotations set readOnlyHint=false for what reads as a query/answer tool, nor does it describe latency or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then a compact table, then when-to-use, then an example. Given 21 parameters and 8 intents this density is justified, though a couple of parenthetical asides ('type:"ask" sends it there') and the repeated window/tslot warning add minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 21-parameter tagged-union tool with nested objects and no output schema, the definition is complete: the table's 'answers' column conveys the return semantics per intent, the error envelope behavior is stated, cross-tool dependencies (emem_trajectory for tslots) are called out, and an example argument object is provided.

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?

Schema coverage is already 86%, so the schema carries most per-field meaning. The description still adds real value with the routing table mapping each `type` to its needs/optional fields, the instruction to send only the fields in the row, the note that `window` values are epoch-relative tslots (not unix/date strings), and a worked example. It stops short of documenting every field, so it complements rather than replaces the schema.

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 states a specific verb and resource ('State what you want in one typed object and get the answer'), then enumerates the eight intent rows with their required/optional fields and answers. It explicitly distinguishes itself from siblings (emem_recall, emem_recall_polygon, emem_ask), so an agent can route without opening other schemas.

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

Usage Guidelines5/5

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

There is an explicit 'When to use' block: use this when the question matches one of the eight rows and you prefer to state the goal, otherwise call the primitive. Concrete alternatives are named per case (a band at a cell -> emem_recall, a region -> emem_recall_polygon, free text -> emem_ask), plus the note that named tools can be invoked through tools/call.

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

Deploy Server

Other Tools