Sutra

Write Sutra observation

write_observation

Save a user-authorized preference, decision, correction, pattern, or project fact.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tags`	No	Optional search tags; at most 10 tags, each no longer than 30 characters.
`cluster`	No	Destination cluster name using letters, numbers, or hyphens.	general
`content`	Yes	The preference, decision, correction, working pattern, or project fact to remember.
`importance`	No	Memory importance from 1 (low) to 5 (critical); use 3 by default.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 2, 2026

addedInput schema / properties / cluster / description

Added value: +"Destination cluster name using letters, numbers, or hyphens."

addedInput schema / properties / cluster / maxLength
```
Added value: +50
```
addedInput schema / properties / cluster / minLength
```
Added value: +1
```
addedInput schema / properties / cluster / pattern
```
Added value: +"^[A-Za-z0-9-]{1,50}$"
```

addedInput schema / properties / content / description

Added value: +"The preference, decision, correction, working pattern, or project fact to remember."

addedInput schema / properties / content / maxLength
```
Added value: +2000
```
addedInput schema / properties / content / minLength
```
Added value: +1
```

addedInput schema / properties / importance / description

Added value: +"Memory importance from 1 (low) to 5 (critical); use 3 by default."

addedInput schema / properties / tags / description

Added value: +"Optional search tags; at most 10 tags, each no longer than 30 characters."

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "status": {
+    "enum": [
+      "saved",
+      "duplicate"
+    ],
+    "type": "string"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "status"
+]
```

First observedSep 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a non-destructive but non-idempotent write. The description adds the user-authorization constraint, which is useful, but says nothing about duplicate handling, whether existing memories are modified, or how the target cluster affects storage — notable given idempotentHint=false.

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?

A single compact sentence with the action front-loaded and zero filler. It is well-sized for the tool, though the brevity leaves room that could have carried useful behavioral detail.

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?

An output schema exists so return values need not be described, and the annotations carry the safety profile. Still, for a memory-writing tool whose effects persist across the workspace/cluster model, the description is thin on what a saved observation affects and how the cluster and importance parameters shape the outcome.

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 description coverage is 100%, so tags, cluster, content, and importance are all fully documented in the schema. The description's enumeration of savable content types roughly mirrors the content parameter and adds no additional syntax, format, or constraint detail, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ("Save") and enumerates the resource types being persisted (preference, decision, correction, pattern, project fact), so the tool's role is legible at a glance. It is distinguishable from the read-oriented siblings (search_memory, read_context), though it never names the "observation" resource the title uses.

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

Usage Guidelines3/5

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

The phrase "user-authorized" is a meaningful gating condition, implying the agent should only persist content the user has endorsed. However, there is no explicit when-to-use versus alternatives guidance and no statement of prerequisites, so usage is only implied rather than spelled out.

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

All Sutra tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?