Skip to main content
Glama

Duplicate a block

duplicate_block
Read-only

Copy a block with a fresh id. The copy is inserted directly after the original.

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": {
      "document": "<document>",
      "blockId": "<blockId>"
    },
    "name": "duplicate_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockIdYesThe id of a block in the document.
documentYesThe Publisle document: an object with schemaVersion and blocks, as returned by the other tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real behavioral information beyond the annotations: the copy gets a fresh id and is placed immediately after the original, which explains why the operation is non-idempotent and clarifies placement. However, it does not say whether the modified document or just the new block is returned, or what happens if blockId is absent, which matters given the readOnlyHint:true annotation and the passed-in document object.

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?

Two short sentences with zero filler, and the most important fact (fresh id) is front-loaded. Nothing is redundant or buried.

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?

For a two-parameter tool that accepts a nested document object and has no output schema, the definition covers what the tool does but leaves the return value and error behavior unspecified. An agent could call it, but would not know what to expect back or how failures surface.

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 100%, so both parameters (document, blockId) are already documented in the schema. The description adds nothing further about parameter format or constraints, so the baseline 3 applies.

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 ('Copy a block') and adds a concrete outcome ('fresh id'). An agent can distinguish it from add_block or move_block by the fact that it operates on an existing block, though the description never names an alternative explicitly.

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?

Usage is implied rather than stated: you use it to replicate an existing block in place. There is no guidance on when to prefer it over add_block (creating new content) or move_block, and no mention of preconditions such as the blockId being valid in the supplied document.

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