Skip to main content
Glama

mnemon_vector_stats

Inspect vector indexes across pgvector tables to measure memory savings, quantization ratios, and disk usage per tenant.

Instructions

Inspect vector index memory savings, quantization ratios, and disk usage across pgvector tables.

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

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier

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 provided, the description must carry behavioral disclosure. "Inspect" implies a non-destructive read, and "across pgvector tables" conveys scope, but it does not say whether results are per-table or aggregated, whether it requires the pgvector extension, or whether the call is expensive on large clusters.

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?

One dense sentence, front-loaded with the verb and followed by the three metric categories; every word carries information. It could be marginally sharper about scope (per-table vs. aggregate) but there is no filler.

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?

It is a one-parameter read tool with no output schema, and the description names the three categories of metrics the agent will receive, which is enough to decide whether to call it. Remaining gaps (result shape, per-table granularity, cost) are modest for a tool this simple.

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?

There is a single parameter with 100% schema description coverage ("Database tenant identifier"), so the schema already documents it fully. The description adds no extra meaning about tenant scoping or whether the tenant must exist, 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?

"Inspect vector index memory savings, quantization ratios, and disk usage" pairs a specific verb with a concrete resource and enumerates the exact metrics returned. It is clearly distinguishable from mnemon_vector_quantize (an action) and mnemon_cdc_stats (a different metric family), though no sibling is named explicitly.

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 says what the tool reports but never states when to reach for it, when not to, or which sibling to prefer (e.g. mnemon_vector_quantize for applying quantization vs. this tool for measuring its effect). Usage is only inferable from the tool's name and purpose.

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