Turbo Quant Memory MCP Server

by Lexus2016

Overview Schema Source Related Servers Discussions Admin

recent_context

Retrieve recently updated notes, including handoff notes, without a search query to see where you left off when resuming a session or after context compaction.

Instructions

Query-free session bootstrap: the most recently updated notes.

Call this FIRST when starting a new session or resuming after a context compaction, when you do not yet know what to search for. Returns notes ordered by recency (newest first), NOT by relevance — including handoff notes (episodic tier), which a plain semantic_search hides by default. This is the reliable "where did I leave off" entry point.

scope: 'project' (default), 'global', or 'hybrid'. Use 'hybrid' to also surface promoted cross-project knowledge. tier_filter: defaults to all tiers (so handoffs are included). Pass e.g. ["durable"] to exclude episodic session notes. format: 'json' (default); 'text' — compact plain text, one line per note with its hydrate handle (about 20% of the JSON size); 'hook' — the same text as Claude Code SessionStart hook output. Use 'hook' from a SessionStart mcp_tool hook: Claude Code shows the model only an mcp_tool hook's JSON additionalContext, never its plain text.

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": "recent_context"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`scope`	No	project
`format`	No	json
`tier_filter`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.1Nov 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the sort order, that episodic/handoff notes are surfaced by default, what tier_filter does to that default, and the size tradeoff of 'text' (~20% of JSON). The notable gap is that server-side truncation relative to limit and any side-effect expectations are left unstated, though "query-free" implies a read.

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 purpose and the first-call directive are front-loaded before the per-parameter block, which is the right structure. The format entry runs long — the SessionStart hook rendering quirk takes two sentences — but each sentence carries information an agent could not infer elsewhere.

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?

An output schema exists, so return shape needn't be restated, and the description still conveys ordering, the text-format size, and the hydrate handle available in text output. The only meaningful omission for a four-parameter bootstrap tool is the limit parameter and whether results are truncated.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: scope's three values with the meaning of 'hybrid', tier_filter's default and a concrete example, and all three format values with their tradeoffs are explained. The limit parameter is never mentioned, leaving one of four parameters to the bare schema title.

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?

"Query-free session bootstrap: the most recently updated notes" names the resource, the ordering, and the intent in one line. It explicitly separates itself from semantic_search by noting recency-vs-relevance ordering and that handoffs are included rather than hidden, so an agent can pick between the two without opening either schema.

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?

"Call this FIRST when starting a new session or resuming after a context compaction, when you do not yet know what to search for" gives an explicit trigger condition, and the format section adds a second trigger (SessionStart mcp_tool hook). The exclusions are equally explicit: semantic_search hides handoffs, and plain semantic relevance ordering is not what this returns.

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