Skip to main content
Glama

verify_playbook

Read-onlyIdempotent

Audit a playbook's dataflow and configuration without running it. Checks input mappings, step output references, sandbox network/secret usage, and metaphor.tool/agent/dataTable ids. Use after create_playbook or update_playbook, or before run_playbook, when diagnosing wiring issues in automations such as weekly reports, lead enrichment, invoice approval, or ticket triage.

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": {
      "id": "<id>"
    },
    "name": "verify_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlaybook ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered; the description's real contribution is "without running it," which tells the agent no execution or side effects occur during the audit. It also discloses the audit's scope of inspection. It does not say what the result looks like (findings vs. pass/fail) or whether there are cost/time limits, leaving a modest gap.

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?

Two sentences, front-loaded with the core action and scope, then the check list, then usage timing. Every clause is informative, though the trailing example automations (weekly reports, lead enrichment, invoice approval, ticket triage) run a bit long for the marginal retrieval value they add.

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?

For a one-parameter read-only tool this covers purpose, scope, and timing well. The one substantive omission is return behavior: with no output schema, the description never indicates whether the audit returns a list of problems, a boolean, or structured findings, which an agent needs to plan its next step after a failed verification.

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?

There is a single required parameter whose schema description is present at 100% coverage ("Playbook ID"), so the schema already carries the semantics. The description adds no format, source, or acquisition hint for the id (e.g., that it comes from create_playbook or get_playbook), so it does not meaningfully exceed the schema baseline.

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 ("Audit a playbook's dataflow and configuration") and immediately scopes it with "without running it," which cleanly separates it from run_playbook. It then enumerates the concrete checks (input mappings, step output references, sandbox network/secret usage, tool/agent/dataTable ids), so an agent knows exactly what the audit covers without opening anything else.

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?

Gives explicit lifecycle placement: after create_playbook or update_playbook, or before run_playbook. This is a when-to-use rule keyed to named siblings rather than vague advice, and it adds the diagnostic trigger ("when diagnosing wiring issues"). No when-not is stated, but the surrounding conditions make the boundary unambiguous.

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