Skip to main content
Glama
Beever-AI

Beever Atlas

Official

search_memory

Find facts across multiple team communication channels by searching with keywords or natural phrases, returning ranked results even when the exact channel is unknown.

Instructions

Find facts ACROSS MANY channels by hybrid (BM25 + vector) search when you do NOT know which channel holds the answer. Call it first for broad recall, then drill into a specific channel with the tools below.

Routing rule for the three search tools:

  • search_memory(scope='all') — unknown channel; fans the search across every channel the principal can access and merges/ranks the hits.

  • search_channel_facts(channel_id) — known channel; same hybrid search, scoped to one channel, returning the richer per-fact shape.

  • search_memory(scope='channel:') — single channel with the search_memory hit shape (use search_channel_facts instead if you want author/permalink/topic_tags on each row). For a synthesized ANSWER rather than rows, use ask_channel.

Prerequisites: none for scope='all'; a channel_id (from list_channels) for scope='channel:'.

Returns (instant for one channel, longer when fanning across many; read-only): {hits: [{fact_id, text, score, channel_id, cluster_id, entity_tags}, ...], query: <echo of query>} ranked by hybrid score. No side effects.

Error modes (returned as dicts): 'authentication_missing' (no principal); 'invalid_parameter' (empty/over-4000-char query, or scope not 'all'/ 'channel:'); 'channel_access_denied' (only for an explicit 'channel:' the token cannot reach — under scope='all' unreachable channels are silently skipped).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query, keyword or natural phrase, 1-4000 chars (e.g. 'who owns billing'). Longer queries return error 'invalid_parameter'. Required.
scopeNoSearch scope. 'all' (default) = every channel the principal can access; 'channel:<id>' = one channel only (e.g. 'channel:ch-eng').all
limitNoMax hits across the merged result set, 1-50 (out-of-range values are clamped). Default 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses read-only behavior, no side effects, performance hints (instant vs longer), error modes as dicts, and return shape. With no annotations provided, the description fully covers behavioral expectations.

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 bullet points and code blocks. Every sentence adds value. Front-loaded with core function and usage note. Routing rule is efficiently presented.

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?

Covers prerequisites, behavior, returns, error modes, and performance. With output schema present, description is complete for a complex tool with multiple scopes and error conditions.

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?

Adds significant meaning beyond schema: query length constraint with error, scope options with examples, limit clamping. All three parameters are elaborated with context.

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 'Find facts ACROSS MANY channels by hybrid search' when channel is unknown. It distinguishes from siblings like search_channel_facts and ask_channel, providing a specific verb and resource.

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?

Provides a detailed routing rule for three search tools, explaining when to use each. Includes prerequisites and explicit guidance: 'Call it first for broad recall, then drill into a specific channel'.

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/Beever-AI/beever-atlas'

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