TeamShared

memory_playbook_set

Alias for memory_procedure_set.

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"]}
`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.

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

D1.7/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, ownership inheritance, verification window semantics, or return behavior. Calling it an alias is renaming, not explanation.

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

Conciseness2/5

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

The one-sentence description is short, but this is under-specification rather than efficient writing. It spends its only sentence on the alias instead of anything actionable.

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

Completeness1/5

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

For an 8-parameter tool with no behavioral description, the definition is incomplete. The output schema helps with return shape, but the agent is still missing what the tool does, its side effects, and when to use it.

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 the baseline applies. The description adds nothing about parameters, but the schema fully documents each property, including owner_id inheritance and verification_days options.

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 identifies the tool as an alias for `memory_procedure_set`; it never states the operation or resource. An agent must already know what `memory_procedure_set` does, so the purpose is only indirectly implied.

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

Usage Guidelines1/5

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

No when-to-use guidance is provided, no comparison to siblings like `memory_playbook_get` or `memory_playbooks_list`, and no exclusions. The alias statement offers no decision support for choosing this tool.

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.