Skip to main content
Glama

Load a playbook

get_playbook
Read-onlyIdempotent

Retrieves the matching Whalory playbook section for a task from an anchor or free-text query in English or Persian, returning steps, questions, references, output, QA, and alternatives.

Instructions

Return the Whalory playbook section for a task (steps, questions, references, output, QA). Accepts a playbook anchor such as 'caption' or a free-text task in English or Persian; returns the best match and up to limit-1 alternatives.

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": {
      "task": "<task>"
    },
    "name": "get_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesA playbook anchor such as 'caption', or the task in English or Persian
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds genuine behavior beyond that by disclosing fuzzy best-match retrieval with ranked alternatives capped at limit-1, but it omits what happens when no match is found or how confident a match must be.

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?

A single compact sentence pair with no filler: the returned content is front-loaded, followed by the accepted input forms and the matching behavior. Every clause carries information an agent needs, and nothing is repeated from the schema or annotations.

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 does the necessary work of telling the agent what comes back (sections plus ranked alternatives) and what inputs are valid. For a two-parameter, one-required read tool this is close to sufficient; only the no-match edge case and the response envelope remain undisclosed.

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 only 50% — 'task' is documented inline, but 'limit' has no schema description. The description partially compensates by explaining that limit yields the best match plus up to limit-1 alternatives, which clarifies the parameter's semantics beyond its integer bounds. It does not add anything to 'task' beyond what the schema already says about anchors and English/Persian.

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 opens with a specific verb and resource ('Return the Whalory playbook section for a task') and enumerates what the section contains (steps, questions, references, output, QA). It also states the accepted input forms and return shape. It stops short of naming a sibling such as get_reference_section, so the playbook-vs-reference distinction must be inferred from the resource noun alone.

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 implied rather than stated: the tool is for getting a playbook 'for a task', and the accepted anchor or free-text input is described. There is no explicit when-to-use versus when-not-to-use guidance and no routing to the closely named get_reference_section sibling, leaving the agent to infer the boundary.

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