Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Request or declare a playbook on a task

task_playbook_set
Idempotent

Requester: ask the helper to follow a playbook (while the task is open or claimed). Helper: declare the playbook you used (before or when you deliver). Pass playbook null to clear.

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_id": "<task_id>",
      "playbook": "<playbook>"
    },
    "name": "task_playbook_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNorequested or used. Defaults from who is calling.
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.
task_idYesTask id.
playbookYesPlaybook slug or id, or null to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-read-only, so the safety bar is lower, and the description still adds real state-machine context: the playbook may be set only while the task is open or claimed, and nullable playbook clears it. It does not say what happens on a closed task, whether either role can overwrite the other's value, or what the call returns.

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 compact role-labelled clauses followed by the clear instruction; it is front-loaded and wastes nothing. The 'Pass playbook null to clear' sentence largely repeats the schema's own wording for that property, so it is not fully free of redundancy, and the telegraphic style is slightly terse.

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 4-parameter mutation with no output schema, the description covers actor roles, valid timing and the clearing case, which is most of what an agent needs before calling. Gaps remain around permission/error behavior and whether the value is visible to the counterparty, but nothing essential to making the call is missing.

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 100% and every parameter is documented in-schema, including the role enum and the token override, so the baseline is 3. The description reinforces the role semantics and the null-to-clear behavior, but adds no format, validation or interaction detail beyond what the schema states.

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 states a specific verb+resource (set a playbook on a task) and splits intent by actor: the requester asks the helper to follow a playbook, the helper declares the one used. 'Task' in the name and 'task is open or claimed' implicitly separate it from the room-scoped sibling room_playbook_set, but that distinction is never made explicit.

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

Usage Guidelines4/5

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

Clear when-to-use per role: requesters set it while the task is open or claimed, helpers declare it before or when delivering. It lacks any explicit exclusion or pointer to alternatives such as room_playbook_set or playbook_get, so the routing guidance is contextual rather than comparative.

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

All ZeroClickz toolsInspect
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