Quattr

get_playbook

Read-only

Fetch the server-delivered execution playbook for a Quattr workflow, by EXACT workflow id (the skill wrapper knows its own id — this is not a search; use find_relevant_analysis to route questions). Returns the bounded execution core with a version + content hash; never refetch a playbook whose version/hash is already in this conversation. If complete is false or the fetch fails, do NOT improvise the workflow — say the playbook is unavailable and stop before consequential recommendations.

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

Input Schema

Name	Required	Description	Default
`workflow_id`	Yes	Exact workflow id, e.g. "qbr-deck-builder".
`client_contract_version`	No	The wrapper's playbook-contract version (major must match the server's).	1.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, and the description layers on behavior the annotations cannot convey: the return payload (bounded execution core with version + content hash), an idempotency/caching rule, and explicit failure handling ('do NOT improvise... stop before consequential recommendations'). This is exactly the extra context the low annotation bar calls for.

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 dense but front-loaded passage; the core action leads, then routing exclusion, caching rule, and failure protocol follow. Every clause carries operational weight — no filler or restatement of the name.

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 characterizes the return value (execution core + version + content hash) and covers the failure path and caching semantics. An agent has everything needed to call it correctly and to behave properly when it fails.

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 meaning about the workflow_id's provenance — the skill wrapper knows its own id, and this is not a search lookup — which affects how the agent should populate it. It adds modest value beyond the schema's own 'Exact workflow id' note without fully re-specifying the parameters.

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 — fetch the server-delivered execution playbook for a Quattr workflow — and pins the scope to an EXACT workflow id. It explicitly distinguishes itself from search behavior and names the sibling (find_relevant_analysis) used for routing, so an agent can tell it apart from the rest of the catalog 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?

Gives explicit when (by exact workflow id the wrapper already knows), when-not (this is not a search; route questions via find_relevant_analysis), a do-not-refetch rule keyed on version/hash, and a stop-condition when the fetch fails or `complete` is false. Alternatives and exclusions are both present.

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

All Quattr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?