Skip to main content
Glama
Vortx-AI

emem

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

Resolve place to cell64 + band inventory

emem_locate
Read-onlyIdempotent

Convert any place name or coordinates into a canonical cell64 address shared by all agents, then list the data bands and algorithms available for that location.

Instructions

Mint the canonical, vendor-neutral address (cell64) for a real-world place: the shared spatial identity every agent resolves to identically, so two models refer to the same ground instead of two descriptions of it. Also returns the topic-grouped inventory of bands and algorithms recallable there. For a first-class OBJECT identity (a bridge, a plot, a named place) rather than a raw cell, use emem_entity. Send EITHER lat+lng as numbers OR a free-text place; coordinates win when both arrive. q, query and name are all accepted spellings of place. A key this schema does not declare is reported in _unrecognised_arguments, so a typo answers about somewhere else rather than erroring.

When to use: Use whenever the input refers to a real-world location and the next step needs the cell64 identifier or wants to know which bands are available before recalling. The response carries data_at_this_cell with three sub-fields: live_bands_by_topic (every band recallable here, grouped by topic such as flood_water_event_window, vegetation_condition, built_up_human_geography), algorithms_for_topic (composition recipes that fuse those bands into named scores), and declared_but_no_materializer_at_this_responder (cube slots reserved without a live connector). For the single-shot path that runs the full chain server-side and returns one packaged answer, use emem_ask instead.

Example arguments: {"place":"Mount Everest"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for `place`, accepted because OSM/Mapbox/Google Geocoding all use `q`. Provide either this or `place` (or `lat`+`lng`).
latNoWGS-84 latitude in degrees, paired with `lng`. REQUIRED with `lng` unless `place`/`q` is provided.
lngNoWGS-84 longitude in degrees, paired with `lat`. REQUIRED with `lat` unless `place`/`q` is provided.
nameNoAlias for `place`.
placeNoFree-text place name (e.g. 'Mount Everest', 'Tokyo'). REQUIRED unless `lat`+`lng` is provided. Aliases also accepted: `q`, `query`, `name`.
queryNoAlias for `place`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.8
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Alias for `place`.",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Alias for `place`.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.1
    • changedInput schema / properties / q / description
      Previous value: -"Alias for `place` — accepted because OSM/Mapbox/Google Geocoding all use `q`. Provide either this or `place` (or `lat`+`lng`)."New value: +"Alias for `place`, accepted because OSM/Mapbox/Google Geocoding all use `q`. Provide either this or `place` (or `lat`+`lng`)."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the description's added value is context beyond that. It discloses two non-obvious behaviors: a typo in an undeclared key is reported in `_unrecognised_arguments` rather than erroring, and coordinates win when both coordinates and a place name arrive. It also explains the response's three sub-fields, which is useful given no output schema.

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?

The description is longer than average but well-structured: purpose first, then input rules, then when-to-use and response details, then an example. Every section carries necessary content for a spatial-resolution tool with six parameters and no output schema. A minor wordiness, such as the metaphorical 'so two models refer to the same ground instead of two descriptions of it,' is acceptable and aids clarity.

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?

With no output schema, the description takes on the burden of explaining return shape, which it does by naming `data_at_this_cell` and its three sub-fields. It also covers input alternatives, aliases, precedence, error-friendly behavior, and explicit routes to sibling tools. An agent has everything needed to call this tool correctly.

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 description coverage is 100%, so baseline is 3. The description adds value by summarizing that `q`, `query`, and `name` are all accepted spellings of `place`, and that coordinates win when both are supplied. This is a concise cross-field semantic that is not immediately obvious from the individual property 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?

The description names a specific verb and resource: it 'mints the canonical, vendor-neutral address (cell64) for a real-world place' and also returns a topic-grouped inventory of bands and algorithms. It clearly distinguishes itself from emem_entity (object identity) and emem_ask (single-shot full chain).

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?

Explicitly states when to use: 'whenever the input refers to a real-world location and the next step needs the cell64 identifier or wants to know which bands are available before recalling.' It names alternatives and when to choose them: use emem_entity for first-class object identity and emem_ask for the single-shot packaged answer. It also clarifies coordinate vs. text input precedence.

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