Skip to main content
Glama

Check memory storage status

amber_get_store_task_status
Read-onlyIdempotent

Check whether a stored memory task is pending, processing, completed, or errored before listing, searching, deleting, or retrying facts. Poll by task ID or idempotency key to confirm writes finished.

Instructions

Check the processing status of a memory store task. Call this before you list, search for or delete the facts you just stored, or when the user asks whether something was saved. Do NOT hold your reply to the user waiting for completed: an accepted store is already durable and finishes in the background, usually within a minute for a few facts. Not rate-limited. Read-only. Requires an active subscription.

Statuses, and these are the ONLY four: pending (accepted and queued, nothing written yet), processing (facts are being written; some are already stored), completed (every fact written), error (error says why). Poll until completed -- note the ed. The import tool's vocabulary (awaiting_upload, running, complete, failed) was published here by mistake until 2026-09-12; an agent waiting for complete waited for ever.

progress reads Stored N/M memories... while writing. Facts are embedded in one batch and then written one at a time, each write idempotent and retry-safe, so a QUEUE redelivery creates no duplicates. That is Amber retrying internally. A CLIENT retry is different: re-sending the same amber_store_memory call starts a NEW task and stores a second copy, so check this status before resending after a transport error.

Rows become listable and SEARCHABLE as they land, NOT only at completed: a partially written task already has some of its memories retrievable. Wait for completed before concluding a fact is absent.

Returns code: not_found if the task_id doesn't exist or has expired (tasks are pruned after 7 days).

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": "amber_get_store_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoUUID from `amber_store_memory`'s response. Poll this to know when memories are ready to search. Invalid IDs return `code: not_found`. Omit it only if you are passing `idempotency_key` instead.
idempotency_keyNoALTERNATIVE to `task_id`: the key you sent to `amber_store_memory`. Use this when you never received the response and so have no task_id -- which is the exact situation the key exists for. Without it the only way to resolve a key is to re-issue the whole store, which needs the payload you may no longer hold.

Output Schema

NameRequiredDescriptionDefault
errorYesError message if status is error. Null otherwise.
statusYes`pending` queued, `processing` writing, `completed` all facts stored, `error` stopped (see `error`). Rows become listable and searchable AS THEY LAND, not only at `completed` -- a task mid-write already has some of its memories retrievable. Wait for `completed` before concluding a fact is ABSENT, which is the reason to wait; do not assume nothing is stored until then.
task_idYesThe task this report is about.
progressYesHuman-readable progress, e.g. 'Stored 4/14 memories...'. The count increments as memories are written. Null when pending, when completed, AND during the early phase of processing before the first memory is written -- so a null here does NOT mean the task is stuck; poll again.
fact_countYesHow many facts this task was created with. Once status is `completed`, memory_ids.length MUST equal this -- compare them. A shorter list means some facts did not resolve to a stored row, which is a real shortfall and not something to report as a successful save.
memory_idsYesMemory IDs created by this task. Null until completed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "ALTERNATIVE to `task_id`: the key you sent to `amber_store_memory`. Use this when you never received the response and so have no task_id -- which is the exact situation the key exists for. Without it the only way to resolve a key is to re-issue the whole store, which needs the payload you may no longer hold.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / task_id / description
      Previous value: -"UUID from `amber_store_memory`'s response. Poll this to know when memories are ready to search. Invalid IDs return `code: not_found`."New value: +"UUID from `amber_store_memory`'s response. Poll this to know when memories are ready to search. Invalid IDs return `code: not_found`. Omit it only if you are passing `idempotency_key` instead."
    • removedInput schema / required
      Removed value: -[
      -  "task_id"
      -]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "error": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Error message if status is error. Null otherwise."
      +    },
      +    "fact_count": {
      +      "description": "How many facts this task was created with. Once status is `completed`, memory_ids.length MUST equal this -- compare them. A shorter list means some facts did not resolve to a stored row, which is a real shortfall and not something to report as a successful save.",
      +      "type": "number"
      +    },
      +    "memory_ids": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Memory IDs created by this task. Null until completed."
      +    },
      +    "progress": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Human-readable progress, e.g. 'Stored 4/14 memories...'. The count increments as memories are written. Null when pending, when completed, AND during the early phase of processing before the first memory is written -- so a null here does NOT mean the task is stuck; poll again."
      +    },
      +    "status": {
      +      "description": "`pending` queued, `processing` writing, `completed` all facts stored, `error` stopped (see `error`). Rows become listable and searchable AS THEY LAND, not only at `completed` -- a task mid-write already has some of its memories retrievable. Wait for `completed` before concluding a fact is ABSENT, which is the reason to wait; do not assume nothing is stored until then.",
      +      "enum": [
      +        "pending",
      +        "processing",
      +        "completed",
      +        "error"
      +      ],
      +      "type": "string"
      +    },
      +    "task_id": {
      +      "description": "The task this report is about.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "task_id",
      +    "status",
      +    "progress",
      +    "memory_ids",
      +    "fact_count",
      +    "error"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / task_id / description
      Previous value: -"The task_id (UUID) returned by `amber_store_memory` in its response. Each store call produces a unique task_id."New value: +"UUID from `amber_store_memory`'s response. Poll this to know when memories are ready to search. Invalid IDs return `code: not_found`."
  3. Changed1 schema field changedv1.1.1
    • changedInput schema / properties / task_id / description
      Previous value: -"The task_id returned by amber_store_memory."New value: +"The task_id (UUID) returned by `amber_store_memory` in its response. Each store call produces a unique task_id."
  4. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Well beyond the annotations: it discloses durability semantics (an accepted store is already durable), the exact four status values with meanings, background completion timing, no rate limiting, subscription requirement, queue-redelivery idempotency vs client-retry duplicate risk, partial searchability during writing, and 7-day pruning with `code: not_found`. Annotations already cover read-only and idempotent, and the description is consistent with them; minor deduction because return-value detail partly duplicates the existing 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?

Front-loaded with purpose and the key instruction (don't block on completion), and the status vocabulary is laid out cleanly. Some phrasing is editorial rather than informative ('note the `ed`', 'waited for ever', 'That is Amber retrying internally'), which costs a little density but not comprehension.

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 polling tool with an output schema, everything an agent needs is present: when to call, how to interpret each status, how long to wait, what partial results mean, and how expiry/not_found is surfaced. Nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters already document their roles, including the task_id/idempotency_key alternative, so the schema carries the burden. The description reinforces the idempotency_key case indirectly via the client-retry duplicate warning but adds no new syntax or format detail beyond 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?

Opens with a specific verb and resource: 'Check the processing status of a memory store task.' It explicitly separates itself from the similarly-named import/export status siblings by calling out that the import tool's vocabulary ('awaiting_upload', 'running', 'complete', 'failed') was mistakenly published here, so an agent can route correctly without opening 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?

Gives explicit when-to-use ('before you list, search for or delete the facts you just stored', 'when the user asks whether something was saved') and explicit when-not/wait guidance ('Do NOT hold your reply to the user waiting for completed'). It also states the polling rule and the prerequisite of an active subscription, leaving little to inference.

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