TeamShared

memory_playbook_set

Alias for memory_procedure_set. Forwards expected_version.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Playbook name (stable id)
`tags`	No	Tags for discovery
`agent`	No	Override agent identity
`owner_id`	No	Org member UUID. Omit inherits last owner or the writer.
`steps_md`	No	Optional intro markdown before composed skills
`description`	No	One-line summary
`tool_recipe`	No	Ordered skill list: {"skills": ["lint", "ship-pr"]}
`expected_version`	No	Latest active version from memory_playbook_get. Omit to append unconditionally, including to recreate a deleted playbook. A mismatch writes nothing and returns status=conflict. current_version null means no active version remains: omit expected_version and write again.
`verification_days`	No	Verification window: 30, 90, or 180 days; 0 for none. Omit inherits the last window.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / expected_version

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Latest active version from memory_playbook_get. Omit to append unconditionally, including to recreate a deleted playbook. A mismatch writes nothing and returns status=conflict. current_version null means no active version remains: omit expected_version and write again."
+}

Changed2 schema fields changedAug 29, 2026

addedInput schema / properties / owner_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Org member UUID. Omit inherits last owner or the writer."
+}

addedInput schema / properties / verification_days

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Verification window: 30, 90, or 180 days; 0 for none. Omit inherits the last window."
+}

First observedAug 18, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It only notes that it 'forwards expected_version', a concurrency/versioning hint the schema already documents in detail, and says nothing about mutation semantics, ownership inheritance, or consequences of a version conflict.

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

Conciseness3/5

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

Two short fragments with no wasted words, so it is not bloated. However, the extreme terseness is under-specification rather than effective conciseness for a tool with nine parameters.

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

Completeness2/5

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

The tool has 9 parameters and an output schema (so return values need not be explained), but the description still omits what a playbook is, how writes behave, and how it relates to the visible memory_playbook_get/list siblings. Referring to a non-sibling tool leaves an agent unable to fully understand the operation.

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 expected_version is extensively documented in the schema itself, so the baseline is 3. The description adds no parameter meaning beyond what the schema already states.

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

Purpose2/5

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

The description only asserts that this tool is an alias for 'memory_procedure_set', which is not even present in the sibling list, so the agent cannot resolve what the underlying operation does. It never states the verb+resource (create/update a playbook) in its own terms, making it effectively a restatement of identity rather than a purpose.

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?

There is no guidance on when to choose this over memory_playbook_get, memory_playbooks_list, or memory_skill_set, nor any prerequisites or conditions. The alias note implies interchangeability but gives no decision criteria for an agent selecting among the memory_* siblings.

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

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.