Skip to main content
Glama

Apply a dream pass's actions

dream_apply
Destructive

Applies revise, forget, confirm, or flag actions to a started dream in pages of 25, returning per-action results with conflict or error status.

Instructions

Apply actions to a started dream; they are sent in pages of 25.

    Each action is `{op, key, expected_version, new_value?, merged_from?,
    reason, evidence_keys}` with `op` one of revise, forget, confirm or
    flag (`expected_version` is required except for flag, `new_value`
    for revise). Returns one result per action: applied, conflict (the
    entry changed since it was read) or error, plus the forget cap and
    the forgets reserved so far. `report` is stored with the dream.
    

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": {
      "dream_id": "<dream_id>",
      "actions": "<actions>"
    },
    "name": "dream_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportNo
actionsYes
dream_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.7.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, and the description adds real context beyond that: per-action outcomes (applied, conflict, error), optimistic-concurrency via expected_version, and a forget cap with reserved forgets. It does not state whether actions are atomic or partial, or how to resolve a conflict result.

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?

Front-loaded with the core verb and scope before the payload detail, and every sentence carries information. The inline pseudo-schema formatting is dense but readable, with no filler sentences.

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?

Return values are partly explained despite an output schema existing, which is a plus. For a destructive multi-action batch tool with zero schema coverage, it omits critical operating detail: whether partial application is possible, what to do on a conflict, and how large the forget cap is.

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 compensate, and it does partially by spelling out the action object's fields, the op values, and that expected_version is required except for flag and new_value for revise. However, merged_from, reason and evidence_keys are named without meaning, and dream_id and report get only a passing mention.

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?

States a specific verb and resource ('Apply actions to a started dream') and scopes the operation to paginated batches of 25. It also enumerates the action ops (revise, forget, confirm, flag), which incidentally overlaps sibling tool names, but it never says explicitly that this is the batch counterpart to those single-op tools.

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?

'A started dream' implies a prerequisite (dream_start must have run first), which is useful. There is no explicit when-to-use versus when-not guidance, and no pointer telling the agent to prefer this over the individual revise/forget/confirm siblings when batching.

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