recordari

orient

Read-only

Get a bounded orientation snapshot. If stale_count > 0, call audit(mode=stale) before filing new memories. If conflicts_count > 0, call audit(mode=conflicts) to review semantically close memory pairs — candidate-surfacing only, not confirmed contradictions. conflicts_count is a density signal, not a monotonically-decreasing queue: connecting a flagged pair suppresses it, but a later substantive revision to either memory lifts the suppression, so the count can rise again without indicating new drift. pass topic when the session has a known purpose — orient will run a semantic search for the topic within the resolved domain and return a relevant section instead of significant. Omit domain (or pass no domain) to get a cross-domain bootstrap snapshot listing all active domains with their per-domain counts (total_nodes, owned_contradiction_count, owned_superseded_count, others_change_count, other_member_count, stale_count) — use this at session start when you do not yet know which domain to work in; call audit(mode=conflicts) for full contradiction pairs. The owned_* fields (owned_contradiction_count, owned_superseded_count, others_change_count, other_member_count) are computed only for authenticated callers with a personal identity (scope=mine or scope=user:); they are always 0 for plain workspace-key sessions (scope=all). stale_count is always populated regardless of scope. Pass a domain to get the full orient response for that domain: rules — up to 20 standing constraints and durable decisions (node_kind='standing') ordered by inbound connection count DESC; always present (empty array when none); rules_count gives the true total — when rules_count > len(rules), call search(node_kind='standing', domain=X) to retrieve the full set. declared_spine — memories with occurred_at set, sorted chronologically (up to 20); these are the curated significant decisions that shaped the domain. significant (when topic is absent) — up to 10 structurally load-bearing memories ranked by recency-weighted importance; these are the memories the domain currently depends on most. relevant (when topic is supplied) — up to 10 memories semantically matched to the topic; replaces significant. recent — the most recently updated memories by the caller (owner-scoped by default; domain-wide when scope=all); shows where your active work is happening. digest (present when scope is personalised) — since-you-were-last-here summary: others_change_count, other_member_count, members list, owned_contradiction_count and owned_contradictions (conflict pairs where the caller owns at least one memory), owned_superseded_count and owned_superseded (archived memories you owned that another member superseded — read from supersedes relationships, not audit_log). summary_hint — a prompt you can pass to an LLM to synthesise the orient data into a narrative paragraph. Overlap between sections is intentional and meaningful: a memory appearing in both significant and declared_spine is both historically important and structurally central. Returns lean results only — id, label, and a truncated why_matters excerpt; call recall(id) for full content. When a list or section has 2 or more results, each is rendered as a single compact text line — "[id] label — excerpt (domain, node_kind)" — instead of a JSON object; exactly one result is returned as a full object.Multi-entry sections (rules, declared_spine, significant/relevant, recent) render as single-line digest strings at 2+ entries. The response always includes server_version — a stable string identifying the current tool surface. If server_version differs from a previously cached value, call tools/list again before issuing any tool calls — the tool surface has changed and your cached schema is stale. Do not call orient again to find more memories — the sections are bounded by design. If you need to find something specific, use search with a targeted query instead.

Input Schema

TableJSON Schema

Name	Required	Description
`scope`	No	Controls whose memories appear in the `recent` section and which contradictions are flagged. 'mine' (default when authenticated) — recent and contradictions scoped to the caller; 'all' — domain-wide, no personalisation (previous default, still the default for plain workspace-key sessions); 'user:<ref>' — view as another member, where ref is a user_id UUID or email address.
`topic`	No	Optional topic for the session. When supplied, replaces the significant section with a relevant section of semantically matched memories (up to 10).
`domain`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It goes beyond annotations with rich behavioral detail: conflicts_count is a density signal, not a monotonically-decreasing queue; suppression mechanics; owned_* fields are zero for plain workspace-key sessions; lean results render as single-line digest strings at 2+ entries; overlap between sections is intentional; server_version staleness handling. This is exactly the kind of non-obvious behavior an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and information-rich, and it front-loads the core purpose well. However, it is very long and covers a lot of output-section detail that is arguably output-schema territory; an agent must parse several hundred words before reaching the action items. Every sentence does earn its place functionally, but the lack of structural formatting (headers, bullets, separation of summary vs edge cases) makes it harder to scan.

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?

For a read-only orientation tool with no output schema, the description fully compensates: it explains return sections, their counts, when they appear, how to handle truncation (rules_count > len(rules) → search), how to get full content (recall), rendering format, scope-dependent fields, and server_version handling. There is no output schema, so this level of descriptive detail is necessary, and it is complete.

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 description coverage is 67%, and for the documented parameters (scope, topic) the schema already provides solid semantics. The description compensates for the undocumented domain parameter with extensive details about passing a domain vs omitting it, and it adds critical behavioral semantics for scope (which fields are computed per scope) and topic (replaces significant with relevant). A slight deduction because the domain parameter itself has no schema description, but the description more than covers its meaning.

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 opens with a specific verb and resource: "Get a bounded orientation snapshot." It then enumerates the exact sections returned (rules, declared_spine, significant/relevant, recent, digest) and how they differ, which clearly distinguishes this tool from siblings like search, recall, and audit. The purpose is unambiguous and grounded in named outputs.

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: omit domain at session start for a cross-domain bootstrap; pass topic for a purpose-driven session; call audit(mode=stale) if stale_count > 0; call audit(mode=conflicts) for full contradiction pairs; use search instead of orient for finding specific memories; and call tools/list again if server_version changed. It also tells the agent when not to call orient again because sections are bounded. This is exemplary routing guidance.

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

All recordari tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

Each tool targets a distinct operation—lifecycle (remember/revise/forget), graph edges (connect/disconnect/why_connected), retrieval (recall/search/recent/history/orient/significance)—and the descriptions carefully disambiguate overlaps. However, the read/analysis cluster (recent, history, orient.recent, significance) could still cause initial misselection before reading the detailed descriptions.

Naming Consistency3/5

Names are readable and consistently lowercase, but they do not follow a single convention: most are bare verbs (connect, remember, revise, search, visualise) while others are nouns (domains, history, recent, significance) and two are multiword phrases (suggest_connections, why_connected). This mix is still predictable enough to navigate, but less coherent than a uniform verb_noun surface.

Tool Count4/5

16 tools is slightly above the typical 3–15 band, but the scope of a knowledge-graph memory server justifies the breadth: CRUD, connections, domain admin, and multiple query/analysis tools are all represented. No tool feels redundant enough to cut, though the set is at the heavy end.

Completeness4/5

Core lifecycle is well covered: create/read/update/archive/purge, connection creation/removal, domain admin, and multiple query/analysis modes. The main gap is that bulk domain merge (merge_domains) is referenced in tool descriptions but not exposed as an MCP tool, so agents must direct users to an external admin interface for that operation.

Resources

Need Help?