Skip to main content
Glama

mnemon_clone_vector

Clone a pgvector HNSW vector index across branches with zero-copy XFS/Btrfs reflink extents, avoiding full index rebuilds.

Instructions

Sub-35ms pgvector HNSW index clone: Duplicates vector index graphs across branches using XFS/Btrfs zero-copy reflink extents.

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": {
      "project_id": "<project_id>",
      "branch": "<branch>",
      "index_name": "<index_name>"
    },
    "name": "mnemon_clone_vector"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesBranch name to clone index from
index_nameYespgvector HNSW index name
project_idYesMnemon project / tenant ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the operation is zero-copy via reflink extents and is sub-35ms. However, it omits critical semantics such as whether the clone is independent copy-on-write or shares extents with the source, what happens if the filesystem lacks reflink support, and whether any permissions are required.

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?

A single dense sentence that front-loads the performance claim and then the mechanism, with no filler. It is efficient, though packing the latency figure and filesystem details into the same clause makes it slightly harder to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with no output schema, the description covers what is being operated on and how, which is nearly enough. The remaining gap is the absence of preconditions and result semantics for a mutation-adjacent operation, but the core behavior is conveyed.

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% with three well-documented parameters, so the baseline is 3. The description adds little beyond the schema; it does not clarify that 'branch' is the source of the clone or how index_name is resolved within it.

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?

The description names a specific verb (duplicates/clones), a specific resource (pgvector HNSW index graph), and the scope (across branches), so it is distinguishable from siblings like mnemon_create_branch or mnemon_vector_quantize. The only weakness is that 'across branches' combined with a 'branch' parameter leaves the direction of the clone slightly ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance: nothing says to prefer this over rebuilding an index, over mnemon_create_branch, or over taking a snapshot. The filesystem precondition (XFS/Btrfs reflink) is stated as a mechanism but not framed as a requirement the agent must verify before calling.

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