Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

recall

Read-onlyIdempotent

Find any memory, note, task, trial, or session by meaning or keyword, scoped to your project and global items. Also browse by memory kind.

Instructions

Search durable knowledge (memories, notes) and the work record (tasks, trials, session findings) by meaning and keyword (fused), scoped to the current project plus global items. This is the single search entry point. Work-record hits carry a status (a task's status, a trial's outcome) and match on keyword only. With kind set and no query it lists that memory kind newest-first instead (browse).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoonly memories of this frontmatter kind (e.g. convention); implies memories-only, so any scope that excludes memories is rejected; with no query, lists the kind newest-first
limitNomaximum results (default 10, max 100)
queryNowhat you are looking for; required unless kind is set (kind alone lists that kind newest-first)
scopeNowhat to search (default all)
projectNoproject slug; defaults to the bound session's project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.1
    • changedInput schema / properties / kind / description
      Previous value: -"only memories of this frontmatter kind (e.g. convention); implies memories-only, so scope=notes is rejected; with no query, lists the kind newest-first"New value: +"only memories of this frontmatter kind (e.g. convention); implies memories-only, so any scope that excludes memories is rejected; with no query, lists the kind newest-first"
    • changedInput schema / properties / scope / enum
      Previous value: -[
-  "all",
-  "memories",
-  "notes"
-]New value: +[
+  "all",
+  "memories",
+  "notes",
+  "tasks",
+  "trials",
+  "sessions"
+]
  2. Changed3 schema fields changedv0.4.9
    • changedInput schema / properties / limit / description
      Previous value: -"maximum results (default 10)"New value: +"maximum results (default 10, max 100)"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds meaningful behavioral detail beyond that: fused meaning/keyword search, project-plus-global scoping, keyword-only matching with status on work-record hits, and the browse listing behavior. No contradiction found.

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?

Three dense, purposeful sentences. The main function is front-loaded, followed by the key limitation (keyword-only for work record) and the browse exception. No filler or redundancy.

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?

Strong overall for a read-only search tool: it covers corpora, scope, matching semantics, status presence, and browse mode. However, there is no output schema and the description does not describe the result payload structure or fields, so an agent must infer what a response contains.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining that work-record hits carry a status and match on keyword only, and by clarifying the project-scope default with global items. Most parameter meaning still comes from the schema, but the added semantic context is useful.

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?

States a specific search operation with named corpora ('durable knowledge' and 'work record'), a clear mechanism ('by meaning and keyword'), and a scope ('current project plus global items'). Calling itself 'the single search entry point' clearly distinguishes it from sibling tools like memory_read and notes_read.

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?

Provides clear context: this is the search entry point, and it explains the special browse mode when kind is set without a query. However, it does not explicitly contrast with direct read tools like memory_read or tasks_list, or say when those should be preferred over recall.

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