Skip to main content
Glama

Semantic search status

memory_embed_status
Read-onlyIdempotent

Report semantic search status, embedding model, and count of entries with current vector embeddings to diagnose why memory_search misses entries with no shared keywords.

Instructions

Report whether semantic search is active, which embedding model is used, and how many entries have a current vector embedding.

Use it to understand why memory_search finds (or misses) entries that share no keywords with the query: entries without a current embedding are lexical-only until they are embedded: usually within 15 s by a read/write MCP server's background worker, or by the embed-backfill CLI command. For general counts use memory_stats; to test that the store works, memory_healthcheck. Read-only, takes no arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_embed_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, but the description adds genuinely new behavior: entries lacking a current embedding are lexical-only, and the normal convergence path is a background worker (~15 s) or the embed-backfill CLI. That lag/eventual-consistency detail is the main reason an agent would misread results, and it is disclosed. Minor gap: it does not say what the report looks like when semantic search is disabled.

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?

Outputs are front-loaded in the first sentence and the diagnostic purpose follows immediately. The middle sentence is dense with nested clauses (lexical-only → background worker → CLI), which slows scanning slightly but every clause carries operational information.

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 zero-argument read tool with no output schema, the description fully covers what is returned (activation, model, embedded count) and the timing caveat that explains surprising results. An agent has everything needed to call it and interpret the answer.

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?

There are zero parameters, so the baseline is 4; the statement 'takes no arguments' is consistent with the empty schema but adds nothing the schema does not already show. No penalty applies since there is nothing to misinterpret.

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 first sentence names a specific verb (report) plus three concrete outputs: activation state, embedding model, and count of entries with current vectors. That distinguishes it cleanly from memory_stats (counts) and memory_healthcheck (liveness), which are 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 Guidelines5/5

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

It states the diagnostic scenario directly—explaining why memory_search misses keyword-disjoint entries—and routes the agent elsewhere for general counts and store testing. Both alternatives are named with the condition that selects them.

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