Skip to main content
Glama
Sign In
SharedMemory MCP Server

SharedMemory MCP Server

Official
by sharedmemoryai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_entity

Retrieve the summary, facts, and relationships for a specific entity like a person, project, or concept.

Instructions

Get everything SharedMemory knows about a specific entity (person, project, concept, etc). Returns the summary, all facts, and relationships.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the entity to look up (e.g., 'John Smith', 'React', 'Project Alpha')
volume_idNoVolume ID. Uses default if not set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A3.8/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 cover behavioral traits. It implies a read operation but does not explicitly state it is non-destructive or safe. For a read tool, this is minimally adequate but not fully transparent.

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?

Two sentences with no unnecessary words. Front-loaded with the main purpose, then details returned data. Every sentence earns its place.

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

Completeness4/5

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

Given no output schema, the description specifies what is returned (summary, facts, relationships). It covers the core functionality for a retrieval tool. Could mention limitations or pagination, but not required for this context.

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 descriptions cover both parameters (name and volume_id) with examples and usage notes. The tool description adds context about entity types (person, project, concept), enhancing understanding beyond the schema.

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 verb 'Get' and resource 'entity', specifying it returns summary, facts, and relationships. It distinguishes from siblings like 'get_memory' and 'search_entities' by emphasizing comprehensive retrieval.

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 on when to use this tool versus alternatives like 'get_memory' or 'get_graph'. The description describes functionality but lacks when-to-use or when-not-to-use context.

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