Skip to main content
Glama

vectr_recall

Read-onlyIdempotent

Retrieve notes from current or past sessions using semantic queries or filters. Returns a compact index by default; use note_id or detail='full' to read full bodies.

Instructions

Retrieve notes stored earlier in this session or in prior sessions. TWO-TIER RECALL (UPG-RECALL-HIERARCHY): By default returns a crisp one-line index per note (id + kind/priority + title + age) — token-bounded, safe to call broadly. To read a note body: pass note_id=N (expand one note, full body) or detail='full' (all bodies). Use when vectr_status() confirmed notes_count > 0 — notes may have been stored this session or in a previous one; either way they are immediately useful. Pass a targeted query to retrieve only the notes relevant to your current task — do NOT call with no query unless you need everything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bootNoBoot mode: return ALL directives + high-priority task notes unconditionally (no semantic filter, safe on a fresh workspace). Ignores query/tags/priority/kind/limit.
kindNoFilter to one memory kind: 'directive' | 'task' | 'gotcha' | 'finding' | 'reference' | 'decision' | 'operational'
tagsNoFilter by tags
limitNoMax notes to return (default: 10)
queryNoNatural language query to retrieve only relevant notes (e.g. 'set cartesian product frozenset' returns notes about that task only). Omit only when you need all stored notes.
detailNoDetail level: 'index' (default) = one-line summary per note (id, kind/priority, title, age) — token-bounded; 'full' = full note bodies (use when you need to read all matching notes).index
note_idNoExpand a single note by ID — returns the full body of that note, ignoring query. Use after seeing the index output to read the note you care about. Get IDs from the [#N] prefix in index output.
sort_byNoSort order: 'relevance' (semantic/trust order, default), 'recency' (newest first), 'priority' (high→medium→low then newest), 'chronological' (oldest first — index lines show the creation date instead of a relative age; combine with kind="decision" for an ADR-style decision timeline, or with any other kind/tag filter for the same time-ordered view).relevance
priorityNoFilter by priority: 'high' | 'medium' | 'low'
max_age_daysNoTime filter: only return notes created within this many days.
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description details the two-tier recall, token-bounded index, sorting behaviors, boot mode, and note expansion. This adds significant behavioral transparency.

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?

The description is dense yet highly efficient, front-loading the core purpose and then efficiently covering the two-tier recall, usage guidance, and key parameter hints without waste.

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?

Given the complexity (10 parameters, no output schema), the description fully explains the return format, recall hierarchy, filtering options, and usage context, leaving no significant gaps.

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?

With 100% schema coverage, the baseline is 3. The description adds extra context for several parameters (e.g., query example, note_id ID source, sort_by chronological behavior), warranting a 4.

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 description clearly states the tool retrieves notes from current or prior sessions, with a specific two-tier recall hierarchy (index vs full body). It uses specific verbs and resources, and the purpose is unambiguous.

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 advises when to use the tool (after confirming notes exist via vectr_status) and when not to (calling without query unless needed). It provides clear context but does not explicitly compare to sibling tools, slightly reducing the score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/swapnanil/vectr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server