Skip to main content
Glama

move

Destructive

Move facts between pages, preserving dates and optionally updating descriptions or aliases. Supports atomic batch operations with versioned sources and destinations.

Instructions

Move exact Facts and optionally replace source or existing-destination descriptions, or atomically create a bounded new destination. Preserve Fact dates and leave at least one source Fact. On applied, reuse returned Page Snapshots and receipts; do not verify with read or list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesExact Fact moves validated as one batch. Use one operation per disjoint source/destination pair and include all Facts for that pair in facts; every page path may appear only once across the batch.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.2
    • changedInput schema / $defs / MoveOperation / oneOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "aliases": {
      -        "type": "null"
      -      },
      -      "description": {
      -        "type": "null"
      -      },
      -      "destination_path": {
      -        "type": "string"
      -      },
      -      "destination_version": {
      -        "type": "string"
      -      },
      -      "new_path": {
      -        "type": "null"
      -      }
      -    },
      -    "required": [
      -      "destination_path",
      -      "destination_version"
      -    ]
      -  },
      -  {
      -    "properties": {
      -      "aliases": {
      -        "type": "array"
      -      },
      -      "description": {
      -        "type": "string"
      -      },
      -      "destination_path": {
      -        "type": "null"
      -      },
      -      "destination_version": {
      -        "type": "null"
      -      },
      -      "new_path": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "new_path",
      -      "description",
      -      "aliases"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "aliases": {
      +        "type": "null"
      +      },
      +      "destination_path": {
      +        "type": "string"
      +      },
      +      "destination_version": {
      +        "type": "string"
      +      },
      +      "new_path": {
      +        "type": "null"
      +      }
      +    },
      +    "required": [
      +      "destination_path",
      +      "destination_version"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "aliases": {
      +        "type": "array"
      +      },
      +      "description": {
      +        "type": "string"
      +      },
      +      "destination_path": {
      +        "type": "null"
      +      },
      +      "destination_version": {
      +        "type": "null"
      +      },
      +      "new_path": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "new_path",
      +      "description",
      +      "aliases"
      +    ]
      +  }
      +]
    • addedInput schema / $defs / MoveOperation / properties / aliases / description
      Added value: +"Required initial aliases for a new destination; omit for an existing destination and update them separately with target=page."
    • addedInput schema / $defs / MoveOperation / properties / description / description
      Added value: +"Replacement description for an existing destination or required initial description for a new destination."
    • addedInput schema / $defs / MoveOperation / properties / source_description
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 80,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Replacement source page description to apply with the Fact move.",
      +  "title": "Source Description"
      +}
  2. Changed18 schema fields changedv0.7.0
    • removedInput schema / $defs / Fact
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "basis": {
      -      "description": "Evidence basis: stated for the user's explicit statement; observed only where the Agent Contract permits a repeated behavioral observation.",
      -      "enum": [
      -        "stated",
      -        "observed"
      -      ],
      -      "title": "Basis",
      -      "type": "string"
      -    },
      -    "content": {
      -      "description": "One complete, independently maintainable, single-line assertion.",
      -      "maxLength": 4096,
      -      "title": "Content",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "basis",
      -    "content"
      -  ],
      -  "title": "Fact",
      -  "type": "object"
      -}
    • addedInput schema / $defs / FactSelector
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "basis": {
      +      "description": "Evidence basis: stated for the user's explicit statement; observed for Agent derivation or inference from current visible material.",
      +      "enum": [
      +        "stated",
      +        "observed"
      +      ],
      +      "title": "Basis",
      +      "type": "string"
      +    },
      +    "content": {
      +      "description": "Exact basis and content copied from an existing Page Snapshot.",
      +      "maxLength": 4096,
      +      "title": "Content",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "basis",
      +    "content"
      +  ],
      +  "title": "FactSelector",
      +  "type": "object"
      +}
    • addedInput schema / $defs / MoveOperation / oneOf
      Added value: +[
      +  {
      +    "properties": {
      +      "aliases": {
      +        "type": "null"
      +      },
      +      "description": {
      +        "type": "null"
      +      },
      +      "destination_path": {
      +        "type": "string"
      +      },
      +      "destination_version": {
      +        "type": "string"
      +      },
      +      "new_path": {
      +        "type": "null"
      +      }
      +    },
      +    "required": [
      +      "destination_path",
      +      "destination_version"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "aliases": {
      +        "type": "array"
      +      },
      +      "description": {
      +        "type": "string"
      +      },
      +      "destination_path": {
      +        "type": "null"
      +      },
      +      "destination_version": {
      +        "type": "null"
      +      },
      +      "new_path": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "new_path",
      +      "description",
      +      "aliases"
      +    ]
      +  }
      +]
    • addedInput schema / $defs / MoveOperation / properties / aliases
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 6,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Aliases"
      +}
    • addedInput schema / $defs / MoveOperation / properties / description
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 80,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Description"
      +}
    • addedInput schema / $defs / MoveOperation / properties / destination_path / anyOf
      Added value: +[
      +  {
      +    "description": "Canonical existing page path from the current Route Catalog.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / $defs / MoveOperation / properties / destination_path / default
      Added value: +null
    • removedInput schema / $defs / MoveOperation / properties / destination_path / description
      Removed value: -"Canonical existing page path from the current Route Catalog."
    • removedInput schema / $defs / MoveOperation / properties / destination_path / type
      Removed value: -"string"
    • addedInput schema / $defs / MoveOperation / properties / destination_version / anyOf
      Added value: +[
      +  {
      +    "description": "Opaque version from the latest Page Snapshot of this page; pass unchanged.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / $defs / MoveOperation / properties / destination_version / default
      Added value: +null
    • removedInput schema / $defs / MoveOperation / properties / destination_version / description
      Removed value: -"Opaque version from the latest Page Snapshot of this page; pass unchanged."
    • removedInput schema / $defs / MoveOperation / properties / destination_version / type
      Removed value: -"string"
    • changedInput schema / $defs / MoveOperation / properties / facts / items / $ref
      Previous value: -"#/$defs/Fact"New value: +"#/$defs/FactSelector"
    • changedInput schema / $defs / MoveOperation / properties / facts / maxItems
      Previous value: -50New value: +30
    • addedInput schema / $defs / MoveOperation / properties / new_path
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "New direct topics/, areas/, or people/ Markdown path using a canonical slug.",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "New Path"
      +}
    • changedInput schema / $defs / MoveOperation / required
      Previous value: -[
      -  "source_path",
      -  "source_version",
      -  "destination_path",
      -  "destination_version",
      -  "facts"
      -]New value: +[
      +  "source_path",
      +  "source_version",
      +  "facts"
      +]
    • changedInput schema / properties / operations / maxItems
      Previous value: -20New value: +15
  3. Changed4 schema fields changedv0.6.0
    • removedInput schema / $defs / MoveOperation / properties / fact
      Removed value: -{
      -  "$ref": "#/$defs/Fact"
      -}
    • addedInput schema / $defs / MoveOperation / properties / facts
      Added value: +{
      +  "description": "All exact Facts to move between this source/destination pair in one operation; copy them unchanged from the latest source Page Snapshot.",
      +  "items": {
      +    "$ref": "#/$defs/Fact"
      +  },
      +  "maxItems": 50,
      +  "minItems": 1,
      +  "title": "Facts",
      +  "type": "array"
      +}
    • changedInput schema / $defs / MoveOperation / required
      Previous value: -[
      -  "source_path",
      -  "source_version",
      -  "destination_path",
      -  "destination_version",
      -  "fact"
      -]New value: +[
      +  "source_path",
      +  "source_version",
      +  "destination_path",
      +  "destination_version",
      +  "facts"
      +]
    • changedInput schema / properties / operations / description
      Previous value: -"Exact Fact moves; every source and destination path must be unique."New value: +"Exact Fact moves validated as one batch. Use one operation per disjoint source/destination pair and include all Facts for that pair in facts; every page path may appear only once across the batch."
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses atomic creation, preservation of Fact dates, the invariant that at least one source Fact must remain, and the side-effect protocol to reuse returned Page Snapshots and receipts instead of re-reading. These are substantive behavioral traits an agent could not infer from the annotations alone.

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 dense sentences front-load the core action and then pack the critical post-conditions and validation guidance. Every clause earns its place: the operation scope, invariants, and the explicit don't-verify instructions. No filler or redundant restating of schema fields.

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 tool with a complex oneOf operation schema and a nested facts array, the description covers the main behavioral caveats (atomicity, source preservation, date preservation, no post-verification) while the rich input schema covers structural details. Since an output schema exists, the description need not explain return values, and nothing essential 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 description coverage is 100%, so the baseline applies and the schema already documents operations, facts, paths, versions, aliases, and descriptions. The description only adds high-level constraints like bounded new destination and preserving dates, without detailing individual parameters. This is sufficient, but it does not add much beyond the schema.

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?

The opening clause 'Move exact Facts' names the verb and resource immediately, and the two follow-up options (replace source/existing-destination descriptions, or atomically create a bounded new destination) delineate the operation's scope against create/update/rename. It also explicitly distances itself from siblings read/list by instructing the agent not to verify with them after apply.

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?

The description gives clear context for when move is appropriate: moving exact Facts, optionally replacing descriptions, or creating a bounded destination. It explicitly tells the agent what not to do afterwards ('do not verify with read or list'), which is a direct usage exclusion, though it does not compare against update/rename in general terms.

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

Deploy Server

Other Tools