Skip to main content
Glama
Sign In
SharedMemory MCP Server

SharedMemory MCP Server

Official
by sharedmemoryai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_context

Assembles a smart context block from stored memories, returning a pre-formatted string for system prompt injection. Enables persistent memory across tools.

Instructions

Assemble a smart context block from stored memories. Returns a pre-formatted context string ready to inject into a system prompt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
volume_idNoVolume ID. Uses default if not set.
user_idNoUser ID for personalized context
max_tokensNoMax tokens for the context block. Default: 2000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses that the output is a pre-formatted string, but it does not mention behavioral traits such as read-only nature, authentication requirements, or default behavior for missing parameters (though the schema mentions defaults).

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 concise with two sentences: one for action and one for output. It is front-loaded and contains no extraneous information.

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

Completeness3/5

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

Given that the input schema fully documents parameters and no output schema exists, the description adequately explains the purpose and output format. However, it lacks usage guidance and does not explain how the context is assembled from memories in relation to sibling tools, leaving some gaps.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema; the schema already describes each parameter sufficiently. The description's mention of 'stored memories' is generic and does not enhance parameter understanding.

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 that the tool assembles a smart context block from memories and returns a pre-formatted string for system prompts. It specifies the verb 'assemble' and resource 'context block', distinguishing it from sibling tools like get_memory or get_profile.

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?

The description provides no guidance on when to use this tool versus alternatives. Siblings include many memory retrieval tools, but there is no mention of when to prefer get_context over get_memory or query.

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

Deploy Server

Other Tools