Skip to main content
Glama
Doucs91

Hivelore

by Doucs91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mem_get

Fetch full memory details by ID when you know the exact ID or a search returns only a compact hit.

Instructions

Fetch a single memory by its full id with all details.

USE WHEN get_briefing / mem_relevant_to / mem_search returned a compact hit and you need the full body, or when you know the exact id of a memory.

PARAMETERS: id — full memory id (e.g. '2026-04-28-gotcha-flyway-strict-no-ddl')

RETURNS: { id, type, scope, status, confidence, body, anchor, tags, usage }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory id to fetch
session_idNoHook session id to credit this complete read to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.65.0
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Hook session id to credit this complete read to",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but 'Fetch' weakly implies a read and it discloses the return shape. It does not state error behavior for a missing id, nor the optional session-credit semantics that the session_id param implies, leaving meaningful behavioral gaps for a no-annotation tool.

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?

Front-loaded one-line purpose followed by clearly labeled USE WHEN, PARAMETERS, and RETURNS blocks. Every line earns its place with no filler.

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?

No output schema exists, but the description compensates with a RETURNS field list, and the required/optional params are covered between description and schema. Only the session_id parameter's purpose is left entirely to the schema, a minor gap.

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 the schema already documents both params, giving a baseline of 3. The description adds a concrete id format example ('2026-04-28-gotcha-flyway-strict-no-ddl') that helps, but omits any mention of session_id.

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?

States a specific verb+resource ('Fetch a single memory by its full id with all details'), clearly distinguishing it from the compact-hit siblings it names (get_briefing, mem_relevant_to, mem_search). An agent can tell exactly what this returns versus a search hit.

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?

An explicit 'USE WHEN' block names the triggering condition (a compact hit needing the full body) plus the alternative condition (knowing the exact id), and points at the sibling tools that produce compact hits. No inference required.

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