Skip to main content
Glama

What tools exist here, and when to reach for each

emem_tools
Read-onlyIdempotent

Find the right tool by topic or capability, and retrieve a tool's schema and runnable example when the available list lacks what you need.

Instructions

The map of emem's tools, and the one tool that finds all the others. It gives the working loop in order (name, ground, cite, resolve, verify, check for drift). Then it groups every other tool by the question it answers, each with a one-line trigger. Send name for the full schema of one tool and an example that runs. IF YOU SEE A LIST OF 18 TOOLS, IT IS A CURATED SUBSET OF 119, NOT THE FULL SURFACE. Hosts remove _meta, so this text repeats the count. A host that calls only listed tools refuses the rest: connect /mcp/full and follow nextCursor, or use listed_route.

When to use: Call this FIRST when you do not know which tool answers the question. Also call it when your list does not have a capability. A tool that is not in your list can still be on the server. q searches by topic (ndvi, flood, verify). name returns one exact schema. With no arguments, you get the full map. /mcp/full registers the full catalog. emem_ask answers in one call without a choice of primitive.

Example arguments: {"q":"ndvi"}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "emem_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text filter over tool names, titles and trigger text, e.g. `ndvi`, `cloud`, `flood`, `verify`, `token`. Plain lowercased substring over name + title + description + trigger text, not fuzzy and not stemmed: `ndvi` hits, `vegetation index` only hits tools that spell that phrase. Combines with `shape`/`bundle`/`category`/`tier` as AND, so an over-narrow combination answers with an empty catalog rather than an error.
nameNoReturn 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. It SHORT-CIRCUITS: when `name` is set every other argument here is ignored, so `{name, q}` is not a search within one tool. A name this responder does not carry is not an error status, you get a body with `did_you_mean` holding up to five names that share a substring with what you asked for.
tierNoWhich slice to list. Defaults to `all`, so this tool shows the whole surface even when the endpoint advertises only the core loop. Your host may still refuse a tool it did not list. Pass `core` to see only what a default connection advertises.
shapeNoFilter 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; `prose` is a model-written narrative over cited facts; `reading` is text read from a document or image; `identity` is a canonical name for a thing; `token` is a citation handle; `proof` checks one.
bundleNoFilter by the job you are doing. Call with no arguments first to see each bundle and its size.
categoryNoFilter to one category. This is about the shape of the job, NOT about safety: 46 tools outside `write` declare `readOnlyHint: false` because reading a cold address can materialise or mint as a side effect, so `category: "read"` is not a safe-tools filter. Read each result's `annotations.readOnlyHint` for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.4.6
    • changedInput schema / properties / category / description
      Previous value: -"Filter to one category. This is about the shape of the job, NOT about safety: 43 tools outside `write` declare `readOnlyHint: false` because reading a cold address can materialise or mint as a side effect, so `category: \"read\"` is not a safe-tools filter. Read each result's `annotations.readOnlyHint` for that."New value: +"Filter to one category. This is about the shape of the job, NOT about safety: 46 tools outside `write` declare `readOnlyHint: false` because reading a cold address can materialise or mint as a side effect, so `category: \"read\"` is not a safe-tools filter. Read each result's `annotations.readOnlyHint` for that."
    • changedInput schema / properties / tier / description
      Previous value: -"Which slice to list. Defaults to `all`, so this tool shows the whole surface even when the endpoint advertises only the core loop, and an `extended` tool you find here is callable by name through tools/call whether or not your host listed it. Pass `core` to see only what a default connection advertises."New value: +"Which slice to list. Defaults to `all`, so this tool shows the whole surface even when the endpoint advertises only the core loop. Your host may still refuse a tool it did not list. Pass `core` to see only what a default connection advertises."
  2. Changed2 schema fields changedv2.4.5
    • changedInput schema / properties / shape / description
      Previous value: -"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."New value: +"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; `prose` is a model-written narrative over cited facts; `reading` is text read from a document or image; `identity` is a canonical name for a thing; `token` is a citation handle; `proof` checks one."
    • changedInput schema / properties / shape / enum
      Previous value: -[
      -  "scalar",
      -  "timeseries",
      -  "raster",
      -  "geometry",
      -  "vector",
      -  "identity",
      -  "token",
      -  "proof",
      -  "plan",
      -  "file",
      -  "catalog"
      -]New value: +[
      +  "scalar",
      +  "timeseries",
      +  "raster",
      +  "geometry",
      +  "vector",
      +  "prose",
      +  "reading",
      +  "identity",
      +  "token",
      +  "proof",
      +  "plan",
      +  "file",
      +  "catalog"
      +]
  3. Changed1 schema field changedv2.4.4
    • changedInput schema / properties / category / description
      Previous value: -"Filter to one category. This is about the shape of the job, NOT about safety: 13 tools outside `write` declare `readOnlyHint: false` because reading a cold address can materialise or mint as a side effect, so `category: \"read\"` is not a safe-tools filter. Read each result's `annotations.readOnlyHint` for that."New value: +"Filter to one category. This is about the shape of the job, NOT about safety: 43 tools outside `write` declare `readOnlyHint: false` because reading a cold address can materialise or mint as a side effect, so `category: \"read\"` is not a safe-tools filter. Read each result's `annotations.readOnlyHint` for that."
  4. Changed4 schema fields changedv1.3.8
    • changedInput schema / properties / category / description
      Previous value: -"Filter to one category."New value: +"Filter to one category. This is about the shape of the job, NOT about safety: 13 tools outside `write` declare `readOnlyHint: false` because reading a cold address can materialise or mint as a side effect, so `category: \"read\"` is not a safe-tools filter. Read each result's `annotations.readOnlyHint` for that."
    • changedInput schema / properties / name / description
      Previous value: -"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."New value: +"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. It SHORT-CIRCUITS: when `name` is set every other argument here is ignored, so `{name, q}` is not a search within one tool. A name this responder does not carry is not an error status, you get a body with `did_you_mean` holding up to five names that share a substring with what you asked for."
    • changedInput schema / properties / q / description
      Previous value: -"Free-text filter over tool names, titles and trigger text, e.g. `ndvi`, `cloud`, `flood`, `verify`, `token`."New value: +"Free-text filter over tool names, titles and trigger text, e.g. `ndvi`, `cloud`, `flood`, `verify`, `token`. Plain lowercased substring over name + title + description + trigger text, not fuzzy and not stemmed: `ndvi` hits, `vegetation index` only hits tools that spell that phrase. Combines with `shape`/`bundle`/`category`/`tier` as AND, so an over-narrow combination answers with an empty catalog rather than an error."
    • changedInput schema / properties / tier / description
      Previous value: -"Which slice to list. Defaults to `all`, so this tool shows the whole surface even when the endpoint advertises only the core loop."New value: +"Which slice to list. Defaults to `all`, so this tool shows the whole surface even when the endpoint advertises only the core loop, and an `extended` tool you find here is callable by name through tools/call whether or not your host listed it. Pass `core` to see only what a default connection advertises."
  5. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses a non-obvious failure mode: hosts strip `_meta` and refuse unlisted tools, so a visible list of 18 may be a curated subset of 119. It also warns that `category: "read"` is not a safety filter because 46 tools outside `write` set readOnlyHint false — real behavioral context an agent could not infer from the annotations.

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 the one-sentence purpose, then the loop, then the grouping, then argument usage — a sensible order. It is dense rather than padded, though the all-caps subset warning plus the self-referential note 'this text repeats the count' restate the same point and cost some tightness.

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 six-parameter discovery tool with no output schema, the description explains what comes back (tools grouped by the question they answer, each with a one-line trigger), what `name` returns (schema plus runnable example), and what happens on a miss (`did_you_mean` with up to five names). Nothing needed to call it correctly is left implicit.

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 100%, so the baseline is 3 and the schema already carries the enum semantics and the `name` short-circuit rule. The description still adds practical framing: no arguments yields the full map, `q` searches by topic, `name` returns one exact schema, plus a runnable example. It reinforces rather than duplicates, but adds only modestly over the already-rich 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 opening line names a specific role — 'the map of emem's tools, and the one tool that finds all the others' — and the body specifies the two retrieval modes (full map, `q` topic search, `name` exact schema). It also distinguishes itself from emem_ask ('answers in one call without a choice of primitive'), so an agent can tell which of the two to open.

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?

Explicit when-to-use is stated: 'Call this FIRST when you do not know which tool answers the question' and 'Also call it when your list does not have a capability.' An alternative is named and its selection condition given (emem_ask for one-call answers without choosing a primitive), and the edge case of a truncated host list is addressed with concrete remedies (/mcp/full, nextCursor, listed_route).

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