Skip to main content
Glama

Run a GTM Vault playbook

get_playbook
Read-only

Get a GTM Vault playbook or skill by name, for example gtm-audit, tool-check or gtm-vault-caption-pack. Returns its steps and the tools each step uses. Any inputs passed are returned with the steps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
inputsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail beyond them — that the result contains steps plus the tools each step uses, and that supplied inputs are passed through — which tells the agent this is a dry retrieval, not an execution.

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?

Three tight sentences with the core verb and resource front-loaded, followed by return behavior. No filler, though the trailing sentence about inputs would read better attached to the parameter rather than the return value.

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

Completeness4/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 must characterize the response, and it does so concisely (steps plus per-step tools). For a two-parameter, closed-world read tool this is close to sufficient; the only real gap is what 'inputs' are semantically for.

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 coverage is 0%, so the description carries the burden. It does explain both params at a surface level: 'name' by naming the lookup key, and 'inputs' by saying they are echoed back with the steps, but it never says what inputs are for (parameter substitution into steps?) or what key/value format is expected for the nested object.

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

Purpose4/5

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

The description uses a specific verb and resource ('Get a GTM Vault playbook or skill by name') and grounds it with three concrete name examples (gtm-audit, tool-check, gtm-vault-caption-pack). An agent can tell it is a by-name retrieval versus the sibling list_playbooks, though it never explicitly contrasts the two.

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

Usage Guidelines3/5

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

Usage is only implied by 'by name' — there is no explicit statement of when to reach for this instead of list_playbooks or search_vault, and no prerequisites noted. An agent can infer the case (you already know the playbook name) but must do the inference itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources