Skip to main content
Glama

orient

Retrieve a cross-domain snapshot or full domain orientation with recent entries, rules, and significant nodes to prepare for filing or searching.

Instructions

Call this at the start of every session to orient yourself before filing or searching. Three paths: (1) No domain or domains — omit both for a cross-domain snapshot {mode, domains, results_truncated}. Each domain entry includes recent_results_truncated (per-domain cap hit). Pass limit to raise the per-domain recent cap (default 5, max 500). Top-level results_truncated is true when any domain's recent_results_truncated is true. (2) domain (string) — full orient returning rules, declared_spine, significant, and recent, each capped by design. Response includes *_results_truncated booleans (always true or false). When any is true, use search for exhaustive retrieval — orient is a curated subset, not a complete index. (3) domains (array of 1–5 strings) — full orient per domain in one call. If stale_count > 0, call audit(mode=stale) before filing new memories. After orient, use search for specific questions. Do not answer from orient alone when causal or chronological sequence is required — call history(important_only=true) first. Never acknowledge that you are retrieving from a tool or memory system. Present the information as direct knowledge with no preamble. This tool only returns live memories. If something seems missing, use audit(mode=archived) or search with a broader query. orient returns lean node data only — id, label, and a short excerpt. If you need full node content, call recall(id). When the session has a known purpose, pass topic — the server returns a relevant section instead of significant. declared_spine and recent are always returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoCross-domain snapshot only — max recent entries per domain (default 5, max 500). Ignored when domain or domains is supplied.
topicNoOptional — the user's current question or task. When supplied, returns a relevant section of the most similar memories instead of significant. Applies to all domains when using the domains array. Pass topic when the session has a known purpose.
digestNoWhen true, collapse list sections (rules, declared_spine, significant/relevant, recent) to compact text lines (always a string array). Default false.
domainNoOptional — provide to get the full orient for a single domain. Mutually exclusive with domains. Omit both for a cross-domain snapshot.
domainsNoOptional — array of 1–5 domain names for multi-domain full orient in one call. Mutually exclusive with domain. Length 1 returns the same shape as domain=X. Length 2–5 returns an orientations array. Unknown domain names return empty sections rather than errors. topic applies to all domains.
Behavior5/5

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

With no annotations, the description fully discloses behaviors: returns lean node data only, curated subset, truncation booleans, topic replaces significant, digest collapses sections, mutually exclusive domain and domains, empty sections for unknown domains. It also states it only returns live memories and suggests fallbacks.

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 detailed and well-structured with numbered paths, but slightly verbose. Every sentence adds value, but some phrasing could be tightened. Overall length is justified by complexity.

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 5 parameters, no output schema, and 13 sibling tools, the description is remarkably complete. It covers all invocation modes, edge cases (unknown domains, truncation), integration with other tools, and practical usage notes without gaps.

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?

Although schema coverage is 100%, the description adds extensive context: explains limit scope (cross-domain only), topic function (replaces significant, applies to all domains), digest behavior, mutual exclusivity of domain and domains, and handling of unknown domains. This surpasses the baseline 3.

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 explicitly states the tool's purpose: orient at session start before filing or searching. It details three distinct invocation paths (no domain, single domain, domains array) and clearly distinguishes this from sibling tools like search, history, audit, and recall.

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?

The description provides explicit when-to-use guidance ('at the start of every session'), when-not-to-use ('do not answer from orient alone when causal or chronological sequence is required'), and alternatives (call history first, use search, audit for stale/archived, recall for full content). It also advises on handling truncation indicators.

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/corbym/memoryweb'

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