Sutra

Read Sutra context

read_context

Read-onlyIdempotent

Return the user's shared identity context, project clusters, and memories.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`clusters`	Yes
`memories`	Yes
`display_name`	Yes
`last_updated`	Yes
`total_memory_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 2, 2026

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

addedOutput schema / properties

Added value: +{
+  "clusters": {
+    "items": {
+      "properties": {
+        "created_at": {
+          "type": "string"
+        },
+        "description": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "is_default": {
+          "type": "boolean"
+        },
+        "memory_count": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "description",
+        "is_default",
+        "created_at",
+        "memory_count"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "display_name": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "last_updated": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "memories": {
+    "items": {
+      "properties": {
+        "cluster": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "content": {
+          "type": "string"
+        },
+        "created_at": {
+          "type": "string"
+        },
+        "importance": {
+          "type": "integer"
+        },
+        "source_agent": {
+          "type": "string"
+        },
+        "tags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "content",
+        "source_agent",
+        "importance",
+        "created_at",
+        "tags"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "total_memory_count": {
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "display_name",
+  "clusters",
+  "memories",
+  "total_memory_count",
+  "last_updated"
+]

First observedSep 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured fields. The description adds the content scope (identity context, clusters, memories) but says nothing about size, caching, or freshness of the returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. Every word contributes to describing the return scope.

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

Completeness4/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-value detail need not be in the description, and the annotations carry the safety profile. The one gap is the absence of any routing guidance versus the many sibling read tools, but as a parameterless aggregate read it is largely complete.

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

Parameters4/5

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

Zero parameters, so the baseline is 4 per the rubric. The description correctly implies a parameterless, scope-free read, matching the empty schema.

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?

Names a specific verb (return/read) and resource (shared identity context, project clusters, memories), which is clearer than the bare tool name. It does not, however, differentiate itself from siblings like get_cluster or search_memory, though the scope (aggregate context) is implied to be broader.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as search_memory or get_cluster. The agent must infer that this is a bulk/aggregate retrieval versus the more targeted sibling tools.

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 Every Agent Can ShareAgents share what they learn, hand off work, and keep 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?