Skip to main content
Glama
matebenyovszky

AgentPlaybooks

by matebenyovszky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get playbook

get_playbook
Read-onlyIdempotent

Fetch a playbook by ID along with its persona, skill, server, and memory metadata; set include_content to restore full details only when needed.

Instructions

Get a playbook with its singleton persona and compact skill, connected-server and memory metadata. Skill bodies, memory values and server configurations are omitted unless include_content=true. This is the only persona retrieval tool; there is no get_persona. Read-only; requires playbooks:read or full. Use list_playbooks for IDs, get_skill / get_skill_reference for selected instructions and search_memory / read_memory for selected facts.

Input Schema

NameRequiredDescriptionDefault
playbook_idYesUUID of the playbook
include_contentNoRestore the full skill, memory and server payload; prefer targeted reads

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / include_content
      Added value: +{
+  "default": false,
+  "description": "Restore the full skill, memory and server payload; prefer targeted reads",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/no-destroy, and the description still adds meaningful context: the required scope (playbooks:read or full) and the fact that skill bodies, memory values and server configurations are elided by default. The only missing piece is response shape/error behavior, which is minor given no output schema.

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?

Content scope is front-loaded, then the elision rule, then the persona-uniqueness note, then routing. Four dense sentences with no filler and no repetition of schema types.

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?

With no output schema, the description still tells the agent what fields come back and what is suppressed by default, plus permissions and sibling routing. Nothing needed to call this correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: include_content restores the full skill/memory/server payload and should be used sparingly in favor of targeted reads. That explains the tradeoff, not just the type.

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?

States a specific verb and resource and enumerates the returned payload (singleton persona, compact skill, connected-server and memory metadata). It also preempts a likely sibling-name confusion by declaring 'there is no get_persona', so the agent can distinguish it from get_skill and the persona tools without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: list_playbooks for IDs, get_skill / get_skill_reference for selected instructions, search_memory / read_memory for selected facts. The include_content caveat also states the default path and the preferred targeted-read alternative, which is exactly when/when-not guidance.

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

Deploy Server

Other Tools