TeamShared

context_commit

Turn-end batch: assistant summary + durable writes + optional close.

One call replaces the end-of-turn memory_session_append + memory_remember (+ memory_session_close + memory_state_set) sequence. The append self-heals expired sessions; the response's session_id is authoritative. Returns {session_id, turn_count, reopened, memories, closed, org, bound}.

Input Schema

TableJSON Schema

Name	Required	Description
`repo`	No	Workspace slug; scopes fact tags and the state pointer.
`agent`	No	Override agent identity
`close`	No	Close the session (queueing distillation) and clear the state pointer. Pass true when the task is done or the user says goodbye.
`facts`	No	Durable memories to write in the same call: [{"content": "...", "kind": "fact\|preference\|event\|note\|outreach", "subject": "...", "tags": [...]}]. Only include things still true next week.
`github`	No	GitHub owner/repo tag for the facts.
`summary`	Yes	Faithful summary of your reply — appended as the assistant turn.
`namespace`	No	Org-allowlisted container slug (repo:owner/name, github:owner/repo, or project:name). Tags every fact. Omitted: default from github= then repo=. Invalid/unknown slugs fail. See docs/memory-namespaces.md.
`session_id`	No	Working-memory session to commit to. Omit to resolve it from the conversation/active-session state pointer (requires repo).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

addedInput schema / properties / namespace

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Org-allowlisted container slug (repo:owner/name, github:owner/repo, or project:name). Tags every fact. Omitted: default from github= then repo=. Invalid/unknown slugs fail. See docs/memory-namespaces.md."
+}

Changed1 schema field changedAug 30, 2026

changedInput schema / properties / facts / description

Previous value: -"Durable memories to write in the same call: [{\"content\": \"...\", \"kind\": \"fact|preference|event|note\", \"subject\": \"...\", \"tags\": [...]}]. Only include things still true next week."New value: +"Durable memories to write in the same call: [{\"content\": \"...\", \"kind\": \"fact|preference|event|note|outreach\", \"subject\": \"...\", \"tags\": [...]}]. Only include things still true next week."

First observedAug 18, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful traits such as self-healing expired sessions, the response's session_id being authoritative, and the returned fields, but it omits side effects of close (queueing distillation, clearing the state pointer) and any permission or failure behavior.

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?

Four short sentences front-load the one-line summary, then give the replacement relationship, behavioral caveat, and return shape. There is no filler or redundancy.

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?

Given the 8-parameter schema with 100% coverage and an output schema, the description provides the essential selection and behavioral context: when to use it, what it replaces, self-healing behavior, and authoritative session_id. The schema fills the remaining parameter and return-value details, so nothing needed to call it correctly is missing.

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% with detailed parameter descriptions, so the baseline is 3. The description only maps summary/facts/close to 'assistant summary + durable writes + optional close' without adding new syntax or format details beyond the schema.

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 defines the tool as a 'Turn-end batch' combining assistant summary, durable writes, and optional close, and the second sentence names the exact memory_* sequence it replaces. This makes its purpose and distinction from sibling memory tools immediately clear.

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 clearly positions the tool as the end-of-turn replacement for memory_session_append + memory_remember (+ memory_session_close + memory_state_set), so an agent knows when to prefer it. It does not explicitly state when not to use it, such as for mid-turn appends, so it lacks full exclusion guidance.

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.