Skip to main content
Glama
Sign In

OwlMem

by com.owlmem
OverviewDiscussionsAdmin

kb_search

Read-onlyIdempotent

Keyword search of your team's knowledge base (case-insensitive; several words are matched separately and files with more of them rank first). Search before writing to avoid duplicates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "kb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax files to return (default 20, max 50)
queryYesWords to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Text to search for"New value: +"Words to search for"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, yet the description adds real matching semantics: case-insensitivity, per-word matching, and ranking by number of matched words. That is genuine behavioral disclosure beyond the structured fields, though it omits anything about result truncation or why the cap matters.

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?

Two tight sentences with zero filler, leading with the resource being searched and following with matching semantics and the workflow cue. Every clause carries information an agent could act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage and safety annotations, the essentials are present. It still lacks any statement of what a result looks like (paths? snippets?) or pagination behavior, and gives no hint about how this differs from kb_find or kb_recall in an unusually crowded sibling set.

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 baseline is 3 since both query and limit are already documented. The description does add that multiple query words are treated separately rather than as a phrase, which sharpens what "Words to search for" means, but the limit parameter gets no additional comment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Keyword search of your team's knowledge base") and clarifies the matching basis is keywords rather than semantic recall. It does not explicitly distinguish itself from sibling search-like tools such as kb_find, kb_recall, or kb_read, so an agent must still infer which search surface to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides one concrete usage rule: "Search before writing to avoid duplicates," which ties this tool to a workflow with kb_write/kb_retain. However, it offers no when-not guidance and never names an alternative among the many sibling lookup tools, leaving disambiguation to inference.

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

All OwlMem toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources