Skip to main content
Glama

mnemon_vector_quantize

Configure pgvector HNSW-PQ vector quantization and disk-spill indexing to enable billion-scale similarity search while conserving RAM and lowering query latency.

Instructions

Configure pgvector + HNSW-PQ vector quantization with disk-spill indexing for sub-10ms billion-vector search.

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": {
      "tenant_id": "<tenant_id>",
      "table": "<table>",
      "column": "<column>"
    },
    "name": "mnemon_vector_quantize"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTarget vector table
columnYesTarget vector embedding column
tenant_idYesDatabase tenant identifier
dimensionsNoVector dimensions (default: 1536)
disk_spillNoEnable disk-spill indexing for RAM conservation
quantization_typeNoQuantization algorithm (default: PQ)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that quantization and disk-spill indexing are configured, but does not disclose whether the operation rebuilds indexes, requires downtime, affects existing queries, is reversible, or what permissions are needed.

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?

The definition is a single front-loaded sentence with no wasted wording. It is appropriately concise, though the performance claim at the end is more marketing context than essential operational guidance.

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

Completeness2/5

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

This is a complex configuration tool with six parameters and no annotations or output schema. The one-sentence description does not cover operational details such as index rebuild behavior, configuration side effects, defaults, or expected outcomes, leaving the definition incomplete relative to the tool's complexity.

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 all six parameters already have documented semantics in the input schema. The description adds little parameter-level meaning beyond the schema, though it does reflect the disk-spill and quantization concepts that correspond to existing parameters.

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 uses a specific verb ("Configure") and names the exact technologies and resources: pgvector, HNSW-PQ vector quantization, and disk-spill indexing. It clearly explains what the tool does, though it does not explicitly distinguish the tool from related vector or indexing siblings.

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?

The description gives no explicit when-to-use guidance, prerequisites, exclusions, or alternative tools. The performance target ("sub-10ms billion-vector search") provides context but does not tell the agent when this configuration tool should be chosen over other vector-related operations.

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