Skip to main content
Glama

Move a block

move_block
Read-only

Move a block up or down by one or more positions. The block stops at either end.

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>",
      "direction": "<direction>"
    },
    "name": "move_block"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely useful behavioral detail that the annotations cannot express: the move is clamped ('The block stops at either end'), so there is no wrap-around. However, it never resolves the tension between a reordering operation and readOnlyHint=true — the agent is not told whether the passed-in document is mutated or a modified copy is returned, nor whether a move past the edge is a silent no-op or an error.

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 sentences, front-loaded with the action and the axis, followed by the boundary rule. No filler, no restatement of the name or title, and every clause carries information the agent needs.

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 4-parameter tool that takes and presumably transforms a nested document object with no output schema, the description leaves the most consequential question open: what comes back and how it relates to the input document. The boundary-clamping behaviour is a good addition, but the readOnly-plus-document-parameter combination needs one more sentence about return/mutation semantics.

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?

With only 50% schema description coverage, the description usefully compensates: 'by one or more positions' gives meaning and a de-facto default to the undocumented 'steps' parameter, and 'up or down' mirrors the direction enum. The nested 'document' object and blockId are left to the schema, but the key semantic ambiguity an agent would face (how many positions, which way) is addressed.

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 ('Move a block') plus the axis and magnitude of the operation ('up or down by one or more positions'), which cleanly separates it from add_block, remove_block, duplicate_block and update_block. It stops short of naming a sibling or stating that reordering happens within the parent container, so it is clear but not fully differentiated.

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 only implied: the required 'direction' enum and the phrase 'up or down' tell the agent when the tool applies, but there is no explicit when-to-use vs. when-not guidance and no mention of prerequisites such as needing the full document object. An agent can infer the context but is not told, for example, that this cannot cross parent boundaries.

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