Skip to main content
Glama

TeamShared

by io.github.xhad

Memory Recall

memory_recall

Hybrid recall across memory pillars within the caller's org.

Default scope searches durable pillars only (semantic, episodic, procedural, skill, strategic, work). Pass scope=["working"] to include this chat's open session turns. Shared brain on durable pillars: pass agent="cursor" only to narrow semantic/episodic. For entity/competitor questions use a short keyword anchor in query (e.g. "mex") plus repo / github. Use explain=true; prefer hits with matched_keyword: true. Default recall is current truth (superseded/merged rows are omitted); pass include_superseded=true for the replacement chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoMax records to return
repoNoWorkspace slug of your current repo. When set, durable memories tagged for this repo are boosted (ranked higher); nothing is hidden — cross-repo and un-scoped memories still appear. Pass your workspace slug when recalling for code/repo-specific work.
agentNoOptional filter — restrict semantic/episodic results to this agent's writes. Default (None) is the shared brain: every agent's durable memories in the org are visible. Working memory is always scoped to the caller regardless.
queryYesNatural-language query
scopeNoPillars to search. Default (null): durable pillars only (semantic, episodic, procedural, skill, strategic, work) — working is omitted. Add scope=['working'] when you need this chat's open session turns.
githubNoGitHub repository as owner/repo. Boosts memories tagged github:<owner>/<repo> (portable across checkout paths).
explainNoWhen true, include per-record retrieval attribution in metadata
filtersNoOptional AND filter. Keys (all optional): kind (fact|preference|event|note|outreach|skill|procedure), pillar (semantic|episodic|procedural|skill|strategic|work), subject (exact, case-insensitive), tags (list; record must include every tag), since / until (ISO datetimes). Example: {"kind": "fact", "subject": "HolderBrief", "tags": ["decision"]}. Nested AND/OR/NOT is not supported — omit a key instead. Empty result retries once without the filter (filter_relaxed=true on the result). Not for named playbook/skill/entity — use get-by-name tools.
verboseNoWhen false, truncate record content and omit metadata
time_rangeNoOptional time bounds for episodic/working hits
include_supersededNoWhen true, also return superseded/merged history. Default is current truth only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / filters
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional AND filter. Keys (all optional): kind (fact|preference|event|note|outreach|skill|procedure), pillar (semantic|episodic|procedural|skill|strategic|work), subject (exact, case-insensitive), tags (list; record must include every tag), since / until (ISO datetimes). Example: {\"kind\": \"fact\", \"subject\": \"HolderBrief\", \"tags\": [\"decision\"]}. Nested AND/OR/NOT is not supported — omit a key instead. Empty result retries once without the filter (filter_relaxed=true on the result). Not for named playbook/skill/entity — use get-by-name tools."
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_superseded
      Added value: +{
+  "default": false,
+  "description": "When true, also return superseded/merged history. Default is current truth only.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses default durable-only scope, shared-brain visibility, caller-scoped working memory, repo boosting without hiding results, filter relaxation on empty results, and current-truth default with superseded rows omitted. No annotation contradiction exists.

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?

The description is dense but tightly structured, front-loading the core purpose and default behavior before layering conditional usage guidance. Every sentence adds useful information and none are redundant with the schema.

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 complex 11-parameter tool with an output schema and no annotations, the description covers the essential defaults, key behavioral nuances, and routing decisions. The presence of a full output schema means return-value documentation is not required here, and no critical usage gap remains.

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 the baseline is 3, but the description adds meaningful operational guidance beyond the schema: short keyword anchor strategy, preferring matched_keyword:true hits, and clarifying repo/agent scoping effects. This lifts it above baseline though it does not need to re-document each parameter.

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: 'Hybrid recall across memory pillars within the caller's org.' It clearly differentiates from sibling memory tools by stating its recall scope and explicitly excluding named playbook/skill/entity retrieval via 'use get-by-name tools.'

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 gives explicit when-to-use guidance: pass scope=['working'] for session turns, pass agent='cursor' to narrow semantic/episodic, use short keyword anchors for entity/competitor questions, and use explain=true. It also names alternatives by saying 'Not for named playbook/skill/entity — use get-by-name tools.'

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

All TeamShared toolsInspect
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

B3.4/5.0
Disambiguation4/5

With 104 tools across many domains (memory, work, projects, files, agents, context, strategic, ontology), the use of clear prefixes (memory_, work_, project_, file_, agent_run_, context_) makes most tools distinct. However, there are some potential confusions between memory_session_* vs memory_state_*, and memory_recall vs memory_think vs memory_assemble_context, though descriptions clarify their specific purposes. Aliases like memory_playbook_get for memory_procedure_get are explicit and reduce ambiguity.

Naming Consistency5/5

Tool names follow a highly consistent pattern: prefix_domain_action (e.g., file_create, work_update, memory_recall, agent_run_start). All use snake_case, with verbs consistently placed after the domain prefix. Even less common tools like account_brief and attention_snapshot fit the overall naming scheme, making the set predictable and easy to navigate.

Tool Count3/5

At 104 tools, this is an exceptionally large surface area, far exceeding the 25+ threshold that feels heavy. However, the server covers an extensive domain (organizational memory, work management, project tracking, file sharing, agent orchestration, and strategic planning), which justifies a large count. Still, the sheer number may overwhelm agents, and some tools could be consolidated (e.g., many memory_session_* and memory_state_* variants).

Completeness4/5

The tool surface is remarkably complete for its stated purpose, covering CRUD operations for files, work items, projects, and memory, plus lifecycle management for agents, sessions, and strategic plans. Minor gaps exist (e.g., no direct memory_item_get by ID, no section removal in projects), but agents can work around these using existing tools like memory_recall or work_create with parent_id. Overall, the set minimizes dead ends.

Resources