Skip to main content
Glama

search_captures

Search journal entries by concept, keyword, or phrase across all template types to find notes, recall information, or explore topics using natural language queries.

Instructions

Search all journal entries by concept, keyword, or phrase — across every
template type (RC, SYN, REV, DC) at once.

This is the primary way to find entries by idea rather than tag. Use it
whenever the user asks to find notes, recall something they wrote, or
explore a topic. Natural language queries work well.

Examples:
  "neural networks"        → entries mentioning neural networks
  "why does attention"     → entries with that question or phrase
  "spaced repetition"      → concept search across all templates
  "dream flying"           → DC entries with flying imagery

Args:
    query:      The concept, keyword, or phrase to search for.
    tag_filter: Optional tag value to narrow results (e.g. "machine-learning").
    date_from:  Optional ISO date lower bound (e.g. "2025-09-01").
    date_to:    Optional ISO date upper bound (e.g. "2025-12-31").

Note: search matches terms that appear in the journal text. For tag-only
browsing without a text query, use list_by_tag instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
tag_filterNo
date_fromNo
date_toNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining search matches terms in journal text, works across all template types, and handles natural language queries. It could improve by mentioning pagination or result format, but covers core behavior adequately.

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?

Well-structured with purpose statement, usage guidelines, examples, parameter details, and a note - all in compact sentences. Every section adds value without redundancy. The information is front-loaded with the core purpose first.

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 4 parameters with 0% schema coverage and no annotations, the description provides complete context: purpose, usage, behavioral details, parameter semantics, and sibling differentiation. The output schema exists, so return values don't need explanation. This is comprehensive for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 fully. It provides detailed parameter explanations beyond schema titles: query is for concept/keyword/phrase, tag_filter narrows results with examples, date_from/date_to are ISO date bounds with examples. This adds substantial semantic value.

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 searches journal entries by concept, keyword, or phrase across all template types. It specifies the verb 'search' and resource 'journal entries', distinguishing it from sibling tools like list_by_tag which is mentioned for tag-only browsing.

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?

Explicit guidance is provided: use for finding notes by idea rather than tag, when users ask to find notes or explore topics. It distinguishes from list_by_tag for tag-only browsing and provides concrete examples of when to use it.

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/ChavezAILabs/ksj-mcp'

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