Skip to main content
Glama

store_semantic_memory

Save a concept and its definition as a knowledge node in semantic memory, enabling retrieval of timeless knowledge without relying on raw event history.

Instructions

Store a distilled knowledge node in semantic memory.

Stores a distilled CONCEPT/definition (timeless 'what I know'). For a
time-stamped event use store_episodic_memory; for a human-curated palace
note use add_memory_entry.

Semantic memory holds the 'what I know' layer — concepts, definitions,
and their relationships. Used by retrieval to surface relevant knowledge
without relying on raw event history.

Args:
    concept: Short name for the concept, e.g. 'RDT sensitivity' or
        'fAChE inhibition'.
    definition: A one-to-three-sentence definition or explanation.
    related_concepts: Comma-separated names of related concepts.
    source_type: Where this came from: 'paper', 'note', 'idea', or
        'user_defined'.
    source_id: ID of the source record, e.g. a paper DOI or idea_id.

Returns:
    A single TextContent confirming the stored node (its row id and concept
    name), or an error message if the database is missing, fastembed is not
    installed, or the write fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conceptYes
definitionYes
related_conceptsNo
source_typeNouser_defined
source_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool stores a node and returns confirmation or error messages for specific failures (missing database, missing fastembed, write failure). It could mention whether it overwrites duplicates or is idempotent, but overall it is fairly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat long but well-structured: it starts with the core purpose, then usage guidance, then parameter details, then return value. Every sentence adds value, though it could be slightly more concise.

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 five parameters, no nested objects, and an output schema exists (described), the description covers purpose, usage guidelines, parameter semantics, return behavior, and failure modes. It is complete for an agent to use this tool correctly.

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

Parameters5/5

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

The schema has 0% description coverage, but the description's Args section provides detailed explanations for all five parameters, including examples, format, and valid values. This adds significant meaning beyond the raw 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 that it stores a distilled knowledge node in semantic memory, using specific verb and resource. It distinguishes itself from siblings by explicitly mentioning store_episodic_memory and add_memory_entry, and clarifying that it is for timeless concepts.

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 provides explicit guidance on when to use this tool: for timeless concepts/definitions, and when not to use it (time-stamped events or human-curated notes), naming alternatives. This helps an agent choose correctly among siblings.

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/SVerITG/Metis'

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