Skip to main content
Glama
Beever-AI

Beever Atlas

Official
by Beever-AI
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

trigger_sync

Ingest chat channel messages into the knowledge base to make them searchable. Use when retrieval tools return stale results or when a channel refresh is explicitly requested.

Instructions

Ingest a chat channel's messages into the Atlas knowledge base so they become searchable by the retrieval tools (ask_channel, search_channel_facts, search_memory). This is the WRITE/ingestion entry point; it does NOT answer questions — use the retrieval tools for that. It is distinct from refresh_wiki, which only re-renders wiki pages from already-ingested facts.

WHEN TO USE: only when the user EXPLICITLY asks to sync/refresh a channel, OR when retrieval tools return empty/stale results AND the channel was last synced over 24h ago. WHEN NOT TO USE: do not call before every question or as a precautionary warm-up — prefer the data already indexed. Sync is expensive and rate-limited (cooldown) per channel.

PREREQUISITES: get a valid channel_id (and ideally connection_id) from list_channels first. The calling principal must have access to the channel.

LATENCY & SIDE EFFECTS: asynchronous. Returns within ~5s with a job envelope while ingestion runs in the background; this WRITES facts to the knowledge base. Shape: {job_id: 'job_abc123', status_uri: 'atlas://job/job_abc123', status: 'queued'}. Track progress by calling get_job_status(job_id) or reading the atlas://job/ resource.

IDEMPOTENT: if a queued or running sync already exists for the channel, its existing job_id is returned instead of starting a duplicate. A new job is created only when no active job exists, or after the prior one completed or failed.

ERROR MODES (returned as {error: ...}, never raised): 'authentication_missing' (no principal); 'invalid_parameter' (malformed channel_id/connection_id); 'channel_access_denied' (principal lacks access); 'cooldown_active' (synced too recently; includes retry_after_seconds); 'service_unavailable' (backing service down; includes service); 'internal_error' (unexpected failure).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesChannel to sync, e.g. 'ch_eng_backend'. Get it from list_channels. Required.
sync_typeNoSync mode. 'incremental' (default) fetches only messages newer than the last sync (cheap); 'full' re-fetches the entire history (expensive); 'auto' lets the server pick based on sync history. Valid values: 'incremental' | 'full' | 'auto'.incremental
connection_idNoPlatform connection that owns the channel, e.g. 'conn_slack_acme'. Get it from list_channels or list_connections. Default None. Optional but STRONGLY RECOMMENDED when multiple same-platform connections exist (e.g. two Slack workspaces): without it the server matches the channel against each connection's selected_channels pick-list and may mis-route the sync if the channel was never added to a pick-list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: asynchronous (returns job envelope), write side effects, idempotency (returns existing job if queued/running), latency (~5s), error modes (authentication_missing, invalid_parameter, channel_access_denied, cooldown_active, service_unavailable, internal_error), and prerequisite access requirements.

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?

The description is lengthy but well-structured with labeled sections (WHEN TO USE, PREREQUISITES, LATENCY, etc.). Every sentence adds value; no redundancy. Could be slightly more concise, but the structure aids readability.

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 the tool's complexity (3 parameters, asynchronous behavior, idempotency, multiple error modes) and the presence of an output schema (described inline), the description covers all necessary dimensions: purpose, usage, parameters, behavior, errors, and return shape.

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 baseline is 3. The description adds significant context: channel_id is required, sync_type with practical advice (incremental cheap, full expensive), and connection_id with strong recommendation and explanation of mis-routing risk without 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?

The description clearly states the tool's primary action ('Ingest a chat channel's messages into the Atlas knowledge base') and differentiates it from retrieval tools ('It does NOT answer questions — use the retrieval tools for that') and sibling 'refresh_wiki' ('distinct from refresh_wiki, which only re-renders wiki pages').

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 'WHEN TO USE' and 'WHEN NOT TO USE' sections provide clear guidance: only when explicitly requested or when retrieval results are stale and last sync was >24h ago. Also lists prerequisites (get channel_id from list_channels).

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