Skip to main content
Glama
sleepunit-agents

loom

by sleepunit-agents
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

knowledge_recall

Search the memory store by query or exact slug, returning full pages or compact index entries for agent recall.

Instructions

Search the knowledge store with LIKE matching over title, body, and domain, or fetch one page exactly by slug. Never surfaces archived pages. Two detail tiers: "full" returns whole entity pages (the synthesis unit) and stamps last_accessed/hit_count; "index" returns compact slug/domain/snippet entries without stamping. Defaults: full when a query is given, index when browsing without one. Full output is size-guarded — overflow results degrade to index entries; recall by slug to read them. Prefer slug over query when you know the page — token matching can hit cross-references in other pages' bodies.

Input Schema

NameRequiredDescriptionDefault
slugNoExact-slug lookup — returns that single page in full detail and stamps access. Takes precedence over query/domain/limit.
limitNoMaximum results to return (default: 10)
queryNoSearch terms — matched against title, body, and domain. Omit to browse (returns an index of non-archived pages up to limit).
detailNoOutput tier override. "index": compact listing, no body, no access stamping. "full": whole pages with citations. Default: full with a query, index without.
domainNoFilter by domain prefix, inclusive of the exact domain (e.g. "music/gear" matches "music/gear" and "music/gear/elektron")
sort_by_verifiedNoStale-first ordering for the verification engine: verified_at ASC with never-verified pages first. Index entries gain a "verified:" stamp so the SLA filter can run from the listing alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.4.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations are sparse (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description carries the burden and does: it discloses the hidden write side-effect (stamping last_accessed/hit_count, and that index mode does not stamp), the archived-page exclusion, and the size-guard degradation path with its recovery instruction ('recall by slug to read them'). This also explains why readOnlyHint=false despite a read-shaped tool.

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?

Front-loaded with purpose, then scope, then tier behavior, then routing advice — a logical order with no filler sentences. It is dense and slightly packed into a single block, but every clause carries operational meaning.

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?

With no output schema, the description still describes return shapes (compact slug/domain/snippet index entries vs. full pages with citations) and the degradation behavior when results overflow. Nothing an agent needs to call this correctly — defaults, precedence, exclusions, side effects — is missing.

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, but the description adds real semantics beyond it: slug's precedence over query/domain/limit, the detail tier defaults tied to whether a query is present, and the meaning of the access stamp per tier. sort_by_verified gets no narrative treatment, but the schema's own text covers it.

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 two specific verbs (LIKE search over title/body/domain; exact fetch by slug) against a named resource (the knowledge store). It also carves out scope explicitly with 'Never surfaces archived pages', distinguishing it from knowledge_archive/knowledge_history siblings.

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?

Gives explicit when-to-use routing: 'Prefer slug over query when you know the page', plus default behavior for query vs. browse ('full when a query is given, index when browsing without one'). It even explains why slug beats query (cross-reference false hits), which is the kind of reasoning an agent needs to choose correctly.

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