Skip to main content
Glama

get_playbook

Retrieve a step-by-step triage playbook for a specified target type, such as Linux ELF, Windows PE, Android APK, firmware, or packed binaries, to guide reverse-engineering analysis.

Instructions

Get the step-by-step triage playbook for a target type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
scenarioNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; 'Get' plus 'playbook' at least signals a non-destructive read that returns instructional text. It says nothing about output size, whether the playbook is static or context-dependent, or how 'all' behaves, which are meaningful gaps for an unannotated tool.

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?

One short sentence with the resource and its scope front-loaded; every word earns its place and there is no filler to trim.

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

Completeness3/5

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

For a one-optional-parameter read tool with no output schema, the definition is minimally adequate but thin: it omits how this relates to the triage workflow and what the returned playbook looks like. An agent could invoke it, but not with confidence about when it is the right call.

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 0%, so the description must carry the parameter meaning, and 'for a target type' does map the scenario parameter to a target-type selector. However, it never explains the enum values or what the default 'all' returns (combined playbooks vs. something else), so the compensation is only partial.

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 names a specific verb and resource ('Get the ... triage playbook') and scopes it ('for a target type'), which clearly separates it from action-oriented siblings like triage_binary or disassemble_function. It stops short of naming any sibling or contrasting behavior explicitly, so a 4 rather than a 5.

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 when-to-use, when-not-to-use, or prerequisite guidance; nothing says whether this should be called before triage_binary or whether it is a static reference lookup. The only hint is the phrase 'for a target type,' which leaves selection criteria implicit.

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