Tool calls

The Tool Calls view captures every memory operation that runs against your organization. Each remember, recall, forget, and ask call produces one record with the full input, the output, timing, and any error. Use it to debug retrieval, audit usage, or trace what an integration is actually doing. This is distinct from the Audit log — audit log captures state-change events (a namespace was created, an API key was rotated). Tool Calls capture memory operations (every read and write through the gateway).

​

What’s recorded

Each tool call entry includes:

​

Filtering

The Tool Calls page supports filtering by:

• Tool — narrow to one of remember / recall / forget / ask
• Status — successes, failures, or both
• Time range — from / to timestamps

For very busy namespaces, combine filters to surface what you’re looking for. The page paginates; deep history is fully searchable.

​

Common workflows

​

”Why didn’t recall return what I expected?”

1. Open Tool Calls and filter to recall
2. Find the call by query text or timestamp
3. Open the entry — the input shows your exact query and parameters; the output shows the ranked chunks that were returned and their similarity scores
4. If the chunks don’t include what you wanted, check whether the relevant document was ever ingested (filter to remember for the same namespace) or whether it was forgotten (filter to forget)

​

“What sources did ask use?”

Open the ask call’s output payload. The response contains the chunks the synthesizer drew from, with scores. This is the cheapest way to verify citation quality without re-running the call.

​

”Why is my integration failing?”

Filter to Status: Failure and the API key your integration uses. The error message column shows the failure reason — invalid namespace, missing required field, expired key — so you can fix the caller without re-running.

​

”Did this customer’s data get ingested?”

Filter to remember and the customer’s namespace. Each entry shows the document title and source — confirming what was stored without needing to call recall.

​

Performance notes

• Duration is end-to-end from gateway entry to response — including upstream Poros / Peras roundtrips and any LLM calls during ask.
• For ask specifically, expect higher durations (several seconds) since synthesis includes both retrieval and an LLM call.
• Repeated identical-input calls aren’t deduplicated — each call gets its own entry.

​

Retention

Tool Call history is retained per your organization’s plan. Entries are read-only; there’s no way to delete individual records from the console.

​

What’s next