Skip to main content
Glama

Get context

get_context
Read-onlyIdempotent

Retrieve relevant memories and format a pre-rendered context block for any topic or project. Scope by tags, collections, and memory filters.

Instructions

Build a formatted context block for the current topic. Omit topic and collection to show the text collection picker (Memxus menu flow). Call list_collections when unsure of the exact slug. Partial collection names are resolved server-side. If the user's first message appears to be a coding task, technical question, or project-related request, call get_context with the detected topic BEFORE responding — do not wait for the user to ask. After this tool returns, show the user the pre-rendered block at the end of the tool result verbatim (user_facing_template). Do not repeat the raw context_block. Expand context: if count < total, recall/get_context with exclude_memory_ids + higher max_memories; if count === total, say no more memories without calling the server. Skills: use N → use_skill_in_chat, install N → install_skill, skip N → skip_skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags. A tag like project:my-app also sets collection automatically.
typeNoMemory category: general, preference, fact, instruction, or conversation. Omit to include all types.
topicNoSubject to build context for (e.g. "current project", "client meeting notes"). Omit with collection to show the collection picker.
group_idNoUUID of a shared group. Required with visibility=shared when group_name is not set.
collectionNoScope slug (e.g. project:memxus, personal:preferences). GitHub/Notion connector syncs use project:<slug> — one collection per project. Partial names work; call list_collections when unsure.
group_nameNoExact group name (case-insensitive). Alternative to group_id for shared memories.
visibilityNoOptional. Defaults to user dashboard preference (private unless include_group_memories_in_context is on).
max_memoriesNoMax memories in context block. Omit for server default (10). Capped per your plan.
include_skillsNoWhen showing the collection picker, set true if the user chose context + skills (default false).
exclude_memory_idsNoMemory IDs to exclude (for "Ampliar el contexto" follow-up calls).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNocollection_picker when showing the collection selector; omitted for context results.
countYesNumber of memories included.
topicNoTopic that was searched.
totalNoTotal eligible memories for ranking (before LIMIT).
messageYesHuman-readable output (same as content text).
memoriesNoMemories used to build the context block.
truncatedNoTrue when memories were trimmed to the token budget.
collectionsNoCollections shown in picker mode.
tokens_usedNoEstimated tokens in the context block.
context_blockNoFormatted context block for injection into the conversation.
impact_summaryNo
impact_summary_textNoToken reuse line for the AHORRO block when ENABLE_IMPACT_SUMMARY is on.
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint), the description reveals important behaviors: partial collection names resolved server-side, how to present the result (show user_facing_template verbatim), and expansion logic (if count < total, recall with exclude_memory_ids; if count === total, no more memories). Also explains skills handling. No contradictions with annotations.

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 verbose and mixes tool description with agent instructions (e.g., 'Do not repeat the raw context_block'). It is front-loaded with the purpose but contains multiple instructions that could be separated. While comprehensive, it sacrifices conciseness for detail, earning a 3.

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 10 parameters with 100% schema coverage and an output schema, the description adds complete guidance on output handling (user_facing_template verbatim) and expansion logic. It covers the collection picker mode, skills integration, and error handling (no more memories). No gaps are evident.

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 100%, so baseline 3. The description adds extra semantic value: for topic/collection, it explains the picker mode; for collection, clarifies partial name resolution; for include_skills, specifies it's for picker when user chose context+skills; for exclude_memory_ids, ties to follow-up calls. These additions justify a 4.

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 purpose: 'Build a formatted context block for the current topic.' It distinguishes from siblings like list_collections by advising to call it when unsure of the slug, and from recall/update in the expand context section. The purpose is specific and actionable.

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 guidance: 'If the user's first message appears to be a coding task... call get_context with the detected topic BEFORE responding.' Also provides when-not-to: 'Omit topic and collection to show the text collection picker.' Alternatives like list_collections and recall are named. The description covers multiple scenarios thoroughly.

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/gpitrella/memxus-remote-mcp'

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