Skip to main content
Glama

search_shared_memory

Retrieve relevant shared discoveries from agent memory using full-text, semantic, or hybrid queries. Filter by tags, agent, and scope to find prior decisions, fixes, or insights before acting.

Instructions

Primary workflow name for memory search; implemented by knowledge(action='search').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags (action=store, note); for action=search an exact any-of filter in every search mode.
limitNoMax results (for action=search: min 1, values above 100 are capped, 0 or negative is rejected)
queryNoSearch query (for action=search)
scopeNoKG audit scope for action=audit
top_nNoMaximum stale entries returned by action=audit
topicNoSynthesize just this one tag/topic (for action=synthesize). Omit to sweep the densest topics.
lengthNoMaximum details characters returned for action=details
offsetNoCharacter offset for action=details pagination
statusNoStatus filter/update value (open, resolved, archived, superseded)
dry_runNoDry run mode (for action=cleanup, synthesize)
use_llmNoUse the local LLM for the rollup narrative (for action=synthesize, default true; falls back to deterministic when unreachable)
agent_idNoFilter by agent (for action=get, search; omit when using discovery_id readback)
operatorNoBoolean operator for multi-term FTS queries
semanticNoLegacy action=search toggle to force or skip semantic retrieval when supported
severityNoSeverity: low, medium, high, critical (for action=store or action=update)
use_modelNoUse the local model to assess stale entries for action=audit
confidenceNoWriter-supplied confidence for action=store, validated to 0-1; not independently verified or adjusted by governance metrics
epoch_scopeNoStats/list scope: current epoch only or all epochs
min_membersNoMinimum discoveries a topic needs before it is rolled up (for action=synthesize, default 3)
search_modeNoForce retrieval mode for action=search. 'semantic' and 'hybrid' fail honestly when unsupported by the active backend.
include_coldNoInclude cold-storage (long-term) discoveries in search results (default: excluded)
closure_classNoClosing standard for action=update: fix_verified | unobserved | not_reproducible | obsolete | duplicate. 'fix_verified' needs a deployed change whose effect was observed.
response_modeNoRead-envelope mode. Default lean: one-line digests; compact adds diagnostics, full adds raw_governance.lean
discovery_typeNoaction=store; one of architectural_decision, learning, pattern, bug_fix, refactoring, documentation, experiment, question, note, rule, insight, bug_found, bug, improvement, exploration, observation.
including_coldNoInclude cold-storage discoveries in action=list raw status aggregates
memory_contextNoS22 provenance: memory/KG/transcript surfaces visible to the writer
min_similarityNoMinimum cosine similarity for semantic retrieval modes
include_detailsNoExpand results inline only with response_mode='full'; otherwise open one with knowledge(action='details').
max_chain_depthNoMaximum response-chain traversal depth for action=details
closure_evidenceNoEvidence for closure_class. Required keys: fix_verified needs {deployed, observed}; unobserved needs {window, instrument_check}.
continuity_tokenNoOwnership proof from onboard()/identity(), for same-live-process rebinds only. Not a cross-process resume credential.
include_archivedNoInclude archived discoveries in search results (default: excluded)
client_session_idNoIn-session binding id from start_session()/identity(); pass it on same-process calls. Not a cross-process proof.
include_provenanceNoInclude provenance and lineage chain fields in search/details results
exclude_agent_labelsNoOmit search results whose writer display label matches one of these values
include_response_chainNoInclude typed response chain for action=details

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It does not state whether the operation is read-only, whether it can perform other actions like store or update, what happens on failure, or any side effects. The implementation note is the only behavioral hint, and it may mislead the agent into thinking the tool only searches.

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 short and free of fluff, but it is under-specified: it uses an odd nominal phrase 'Primary workflow name' and does not front-load concrete behavioral information. It is concise in length but not in effective communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 36 parameters, no annotations, and no output schema, a one-sentence description is completely inadequate. It fails to mention the broader action surface (store, update, audit, synthesize, details, etc.), return value format, or any operational context. The agent has to infer almost everything from the parameter schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with detailed descriptions for all 36 parameters, so the baseline is 3. The tool description adds no parameter-level meaning beyond noting action='search', which is not a parameter in this schema. It neither supplements nor conflicts with the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says this is a 'Primary workflow name for memory search' and that it is implemented by knowledge(action='search'). This conveys the general purpose (searching shared memory) but is vague about what the tool actually does and how it differs from sibling tools. It borders on restating the tool name and relies on the implementation detail to add meaning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given about when to use this tool versus alternatives. The phrase 'Primary workflow name' weakly implies it is the standard entry point for memory search, and the mention of knowledge(action='search') hints at the underlying implementation, but there are no conditions, exclusions, or comparisons to sibling tools.

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