Skip to main content
Glama

Join two take logs into one

shoot_plan_merge_takes
Read-only

Joins two take logs for the same film into one, for when two phones, an AI assistant and a script supervisor each kept a log while offline. Joining is by op_id, so a take that is in both logs counts once and merging again changes nothing. Where two logs hold different takes under one op_id, only one is kept and the clash is counted, with a fix: give one of them an op_id of its own. The tools take text only, never video or audio, and no AI model runs. Input: a and b, two dpl.takes/1 objects. Output: {takes, merge}: takes is the joined dpl.takes/1 log; merge has added, already_present and conflicts: the counts of entries new to the joined log, entries that were in both, and entries that clashed (a count can be null if the engine did not send it). When conflicts is above 0, merge.conflict_fix says what to do: look before you trust the joined log. We don't keep either take log. Needs an agent key from a Shoot Plan account. Free, and it does not count toward the account's 3 free projects a month. Plans up to 8 MB and 120 calls a minute (5,000 a day).

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "shoot_plan_merge_takes"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesThe first take log (dpl.takes/1).
bYesThe second take log (dpl.takes/1), for the same work_id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses idempotency by op_id, that conflicting entries under one op_id are dropped and counted, that the tool takes text only and runs no AI model, that neither input log is retained, and that an agent key is required. It also lists size and rate limits, which annotations never cover.

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?

Purpose and the join key are front-loaded, and every sentence carries operational information. It is dense and runs long, and the output shape is described at length despite an output schema existing, but nothing is filler.

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?

For a two-object merge tool with nested inputs, the description supplies everything an agent needs: auth requirement, retention behavior, idempotency, conflict handling with a recovery instruction, and quota/rate limits. The presence of an output schema makes the return-value prose redundant rather than necessary, but no calling-critical information 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 both parameters are already documented as dpl.takes/1 objects, so the description's 'a and b, two dpl.takes/1 objects' adds little. It does note that b must be for the same work_id and explains op_id as the join key, but that is conceptual rather than per-parameter guidance.

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 ('Joins two take logs for the same film into one') and immediately scopes it to the offline multi-logger scenario. This is clearly distinguishable from siblings like shoot_plan_validate_takes or shoot_plan_diff, which inspect rather than combine logs.

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?

Gives a concrete when-to-use scenario (two phones, an AI assistant and a script supervisor logging offline) and explains that re-merging is a no-op. It does not name the alternative tools for inspecting or repairing logs (validate_takes, apply_fix), so the routing is implied rather than explicit.

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