TeamShared

memory_remember

Write a durable memory into the caller's org.

fact / preference / note / outreach -> semantic pillar. event -> episodic. procedure / skill -> rejected; use memory_procedure_set / memory_skill_set. Routed through the guarded ingestion pipeline (PII, injection screening, near-dupe merge / contradiction supersede) under RLS. When repo / github are given the memory is tagged repo:<slug> / github:<owner>/<repo>. namespace= (or the default from those args) is an org-allowlisted container — recall with the same slug excludes other namespaces. paths= tags the repo files the memory is about (memory_for_paths reads them). Result includes org + bound.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	fact, preference, event, note, or outreach (not procedure/skill)	note
`repo`	No	Workspace slug of the repo this memory belongs to (e.g. the slug used for memory_state). For code/repo-specific work, pass your current workspace slug so the memory is scoped to this repo (stored as a 'repo:<slug>' tag) and ranks higher when recalled from the same repo. Omit for cross-cutting memories.
`tags`	No	Optional free-form tags
`agent`	No	Override agent identity (defaults to bearer-token identity)
`paths`	No	Repo-relative POSIX file paths this memory is about (e.g. ['src/foo.ts']). Each is stored as a 'path:<p>' tag so memory_for_paths finds it. Absolute paths and '..' escapes are rejected; backslashes and './' are normalized.
`github`	No	GitHub repository as owner/repo (e.g. teamshared-ai/teamshared). Stored as a 'github:<owner>/<repo>' tag for cross-machine association; use with or instead of workspace repo= when the same GitHub repo is checked out at different paths.
`content`	Yes	Free-form text to remember
`subject`	No	Optional subject/entity this memory is about
`namespace`	No	Org-allowlisted container (repo:owner/name, github:owner/repo, or project:name). Tags this write. Omitted: default from github= then repo=. Invalid slugs fail. First write creates the slug on the org allowlist.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / paths

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 20,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Repo-relative POSIX file paths this memory is about (e.g. ['src/foo.ts']). Each is stored as a 'path:<p>' tag so memory_for_paths finds it. Absolute paths and '..' escapes are rejected; backslashes and './' are normalized."
+}

Changed1 schema field changedSep 16, 2026

addedInput schema / properties / namespace

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Org-allowlisted container (repo:owner/name, github:owner/repo, or project:name). Tags this write. Omitted: default from github= then repo=. Invalid slugs fail. First write creates the slug on the org allowlist."
+}

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / github / description

Previous value: -"GitHub repository as owner/repo (e.g. xhad/teamshared). Stored as a 'github:<owner>/<repo>' tag for cross-machine association; use with or instead of workspace repo= when the same GitHub repo is checked out at different paths."New value: +"GitHub repository as owner/repo (e.g. teamshared-ai/teamshared). Stored as a 'github:<owner>/<repo>' tag for cross-machine association; use with or instead of workspace repo= when the same GitHub repo is checked out at different paths."

Changed2 schema fields changedAug 30, 2026

changedInput schema / properties / kind / description

Previous value: -"fact, preference, event, or note (not procedure/skill)"New value: +"fact, preference, event, note, or outreach (not procedure/skill)"

changedInput schema / properties / kind / enum

Previous value: -[
-  "fact",
-  "preference",
-  "event",
-  "note",
-  "procedure",
-  "skill"
-]New value: +[
+  "fact",
+  "preference",
+  "event",
+  "note",
+  "procedure",
+  "skill",
+  "outreach"
+]

First observedAug 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the guarded ingestion pipeline (PII, injection screening, near-dupe merge, contradiction supersede), RLS enforcement, namespace allowlisting with first-write creation, and that the result contains `org` + `bound`. It omits permissions/auth requirements and any irreversibility or rate-limit notes, which keeps it below 5.

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?

The purpose sentence is front-loaded and the kind-routing rule follows immediately, with the heavier behavioral detail later. It is dense but every clause carries information; the pipeline and RLS sentence could be tightened slightly, preventing a 5.

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

Completeness5/5

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

For a 9-parameter write tool with an output schema present, the description covers everything the agent needs: kind routing, rejected kinds and their alternatives, tagging behavior, namespace semantics, and pipeline side effects. Return values need not be explained because an output schema exists.

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% and every parameter is already documented in the schema, including repo->tag, github->tag, paths->tag, and namespace default resolution. The description largely restates this (repo/github tagging, namespace container, paths tags) rather than adding syntax or edge cases beyond the schema, so the baseline of 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?

The opening line gives a specific verb+resource ('Write a durable memory into the caller's org') and the rest of the text maps each `kind` to a storage pillar while naming the sibling tools (memory_procedure_set / memory_skill_set) used for rejected kinds. An agent can tell this apart from memory_recall, memory_session_append, and the *_set siblings without opening any 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?

It explicitly routes kinds: fact/preference/note/outreach to the semantic pillar, event to episodic, and tells the caller to use memory_procedure_set / memory_skill_set instead of passing procedure/skill. It also explains when to pass repo/github versus omitting them ('Omit for cross-cutting memories'). It stops short of an explicit when-to-use-this-vs-memory_recall statement, so it is not a full 5.

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

All TeamShared tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.