What tools exist here, and when to reach for each
emem_toolsDiscover and access all tools in the emem MCP server by name, query, or category. Use this tool first to find the right for Earth observation, search, embedding, and verification tasks.
Instructions
The map of emem's tool surface, and the only tool you need to find the rest. Returns the working loop in the order you walk it (name a thing, ground it, cite it, resolve it, verify it, check for drift), then every other tool grouped by the question it answers, each with its one-line trigger. Pass name to get one tool's full input schema and a runnable example, so you can use a tool without loading all of the descriptors into context. This endpoint advertises the core loop only; the Earth-observation, search, embedding and log tools are catalogued here and remain callable by name.
When to use: Call this FIRST when you do not know which emem tool answers the question, or when you need a capability you cannot see in your tool list. This responder advertises a small core loop by default rather than its full catalog, so a tool being absent from your list does not mean it is absent from the server. Pass q to search by topic (ndvi, cloud, flood, verify), name for one tool's exact schema, or no arguments for the whole map. If you want the full catalog registered as callable tools instead, reconnect to the /mcp/full endpoint; for a one-shot answer without picking a primitive at all, use emem_ask.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free-text filter over tool names, titles and trigger text, e.g. `ndvi`, `cloud`, `flood`, `verify`, `token`. | |
| name | No | Return the full descriptor for exactly this tool (input schema, runnable example, annotations), e.g. `emem_ndvi`. Use this when you already know the name and want its schema without loading the whole catalog. | |
| tier | No | Which slice to list. Defaults to `all`, so this tool shows the whole surface even when the endpoint advertises only the core loop. | |
| shape | No | Filter by what the answer looks like, which is usually the real question. `scalar` is one number at one address; `raster` is a gridded field over an area; `timeseries` is a value per timestep; `vector` is a learned embedding; `identity` is a canonical name for a thing; `token` is a citation handle; `proof` checks one. | |
| bundle | No | Filter by the job you are doing. Call with no arguments first to see each bundle and its size. | |
| category | No | Filter to one category. |