Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

recall

Read-onlyIdempotent

Search durable project and global knowledge plus work records by meaning and keyword to find past decisions, constraints, task statuses, trial outcomes, and session findings.

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

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
sessionNothe session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.4
    • addedInput schema / properties / session
      Added value: +{
+  "description": "the session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless",
+  "type": "string"
+}
  2. 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"
+]
  3. 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"
  4. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive read. The description adds real context beyond that: scope is the current project plus global items, work-record hits carry a status and match on keyword only, and kind-without-query flips to a newest-first browse mode.

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?

Three sentences, front-loaded with the core purpose and scope before the special cases. Dense but every clause carries information; the parenthetical asides add slight clutter but no wasted sentences.

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?

With no output schema, the description usefully notes that work-record hits carry a status. Combined with full schema coverage and read-only annotations, an agent has enough to call it correctly, though return shape and ranking behavior are only lightly touched.

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?

Schema description coverage is 100%, so the parameters are already well documented (including the kind/scope interaction and session semantics). The description largely restates the browse behavior and scoping that the schema already covers, so the baseline 3 applies.

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 verb (search) and enumerates the resources covered (memories, notes, tasks, trials, session findings) via fused semantic+keyword matching. Explicitly positions itself as 'the single search entry point', which distinguishes it from siblings like memory_read, notes_read, and tasks_list.

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?

Declares itself the single search entry point, implicitly routing the agent away from the read/list siblings, and describes the browse alternative (kind set with no query). It does not explicitly say when to prefer memory_read/notes_read/tasks_list instead, so it falls short of a full when/when-not statement.

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