Tools overview

Klio’s surface is deliberately small: one verb per job, so an agent choosing between them does not have to think hard. Every MCP client gets all ten automatically on connection — there is no SDK to wire up.

The ten verbs

Tool	Purpose	Required
`recall`	Retrieve relevant memories before acting	`query`
`remember`	Store a durable fact or preference	`content`
`decide`	Record a decision and its rationale	`content`
`plan`	Record a forward-looking plan	`content`
`observe`	Log what the agent saw or did this session	`content`
`note`	Durable context that is not a fact, decision, or plan	`content`
`artifact_put`	Store a document, JSON record, or file	`title`, `summary`, `kind`
`artifact_get`	Fetch an artifact surfaced by recall	`artifact_id`
`space`	List, create, inspect, or switch spaces	`action`
`forget`	Retract a memory or artifact by id	`memory_id`

Choosing a write verb

The five write tools differ only in the type they record, but that type is what makes recall useful later — a decision and a stray observation should not carry the same weight.

decide — something was chosen

Use whenever an option was picked over alternatives. Pass rationale; a decision without its reasoning gets re-litigated the first time someone disagrees with it.

“We’ll use jittered backoff for 429s, because fixed backoff was synchronising our retries.”

remember — a durable fact or preference

Facts about the project, the stack, or the people. Call it proactively when a user reveals one, not only when asked to.

“The team deploys on Tuesdays.” · “Abhishek prefers TypeScript strict mode on.”

plan — work that is intended

Forward-looking intent, so the next agent can continue rather than restart.

“Next: migrate the auth service to the new token format, then backfill.”

observe — what happened this session

Session activity worth carrying forward. Use sparingly — this is the verb most likely to fill a store with noise. If it will not matter next week, do not write it.

“The integration suite fails on Node 18 but passes on 20.”

note — everything else durable

The catch-all for context that is worth keeping but is not a fact, decision, or plan.

“The legacy/ directory is scheduled for deletion after Q3 — don’t invest in it.”

Common parameters

Every write tool (remember, decide, plan, observe, note) accepts:

'org' | 'agent'

default:"org"

org shares the memory with every agent on the org. agent keeps it private to the identity in the X-Vex-Agent header. See Scope.

string

Optional space slug. Omit to write to the org’s default store.

artifact_put is the one write tool without a scope parameter — artifacts are always org-shared, with no private, agent-scoped equivalent. It does accept space and project. See Artifacts.

What good usage looks like

Agents use Klio well when reading is reflexive and writing is selective:

Before answering questions about this project, call `recall` first.
When a decision is made, call `decide` with its rationale.
When a plan is set, call `plan`.
Do not persist secrets, tool call logs, or file contents.

The failure mode is not too little memory — it is too much. An agent that calls observe after every tool call produces a store where recall returns noise. Write conclusions, not activity.

Overview

Reading

Writing

Artifacts

Managing

Tools overview

The ten verbs

Choosing a write verb

Common parameters

What good usage looks like

​The ten verbs

​Choosing a write verb

​Common parameters

​What good usage looks like

The ten verbs

Choosing a write verb

Common parameters

What good usage looks like