Skip to main content
Glama
mnemostack
by udjin-labs

Mnemostack Answer

mnemostack_answer

Synthesizes a concise factual answer from stored memories instead of returning raw search matches. Use it when you need a direct response with confidence, sources, and token estimates.

Instructions

Answer a question using retrieved memories.

Read-only. Requires the read scope when authentication is enabled. Use this when you want a concise factual answer synthesized from memory search results instead of the raw matches returned by mnemostack_search. Returns a JSON object with ok, query, answer text, confidence (0.0-1.0), sources, notes (the AUTHORITATIVE routine signals — e.g. temporal:no_parse on any query without a date; NOT a fault), degraded (components that actually fell back, plus a deprecated back-compat duplicate of the routine tags until the next major), fallback_recommended, tokens_estimate (estimated text tokens of the context memories), tokens_used (LLM-provider-reported usage for the answer call; null when unreported), and error. Stale facts are hidden by default; use include_invalidated or as_of to see them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "mnemostack_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoPoint-in-time recall (ISO-8601); same contract as mnemostack_search.
limitNoMaximum number of results to return (default 10)
queryYesNatural language question or keyword to search memories for
filtersNoPayload filters applied inside every retriever (exact match or gte/lte ranges); the answer is generated only from memories inside the filtered scope.
token_budgetNoHard cap on the total (estimated) text tokens of the memories fed to the answer LLM (same contract as mnemostack_search). Unset uses the server-wide default.
include_invalidatedNoInclude facts marked stale (default false; same as mnemostack_search).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.3.0
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Point-in-time recall (ISO-8601); same contract as mnemostack_search."
      +}
    • addedInput schema / properties / include_invalidated
      Added value: +{
      +  "default": false,
      +  "description": "Include facts marked stale (default false; same as mnemostack_search).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / token_budget
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Hard cap on the total (estimated) text tokens of the memories fed to the answer LLM (same contract as mnemostack_search). Unset uses the server-wide default."
      +}
  3. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / filters
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Payload filters applied inside every retriever (exact match or gte/lte ranges); the answer is generated only from memories inside the filtered scope."
      +}
  4. Changed2 schema fields changedv0.4.3
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return (default 10)"
    • addedInput schema / properties / query / description
      Added value: +"Natural language question or keyword to search memories for"
  5. First observedv0.4.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description alone carries the safety and behavior burden; it does state 'Read-only' and the read-scope/auth requirement, which is genuinely useful. However, for a tool that spends tokens on an answer call and can degrade, there is a gap around cost/latency and, more importantly, the entire return contract.

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 read-only status, and the notes-versus-degraded clarification is high-value because it prevents misreading routine temporal tags as failures. It is loose as a single dense block, but little of it is expendable for an agent deciding how to call and read the result.

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

Completeness3/5

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

Covers auth, stale-fact defaults, degraded/fallback semantics, and the confidence and token fields, which is substantial. It omits when a caller should prefer fallback_recommended and how confidence should be interpreted, which matters for a synthesis tool whose output is probabilistic.

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%, so all six parameters are already documented in the schema; the description adds only the stale-fact behavior of include_invalidated and as_of. There is no additional meaning offered for filters, token_budget, or limit, so the baseline 3 applies.

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?

States a specific verb and resource ('Answer a question using retrieved memories') and immediately frames the contrast with mnemostack_search's raw matches. An agent can distinguish it from every sibling without opening the schema.

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

Usage Guidelines4/5

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

Explicitly says to use this over mnemostack_search when a synthesized concise answer is wanted rather than raw matches, which is exactly the selection decision. It stops short of stating when NOT to use it (e.g. exhaustive listing, auditing sources), so it falls one step short of full routing guidance.

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